<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/mmc/core, branch linux-2.6.29.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.29.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.29.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2009-03-08T13:46:04Z</updated>
<entry>
<title>mmc: fix data timeout for SEND_EXT_CSD</title>
<updated>2009-03-08T13:46:04Z</updated>
<author>
<name>Adrian Hunter</name>
</author>
<published>2009-02-10T14:32:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cda56ac29f2d8288d62978272856884d26e0b47b'/>
<id>urn:sha1:cda56ac29f2d8288d62978272856884d26e0b47b</id>
<content type='text'>
Commit 0d3e0460f307e84904968aad6cff97bd688583d8
"MMC: CSD and CID timeout values" inadvertently broke
the timeout for the MMC command SEND_EXT_CSD.

This patch puts it back again.

Depending on the characteristics of the controller,
this bug may prevent the use of MMC cards.

Signed-off-by: Adrian Hunter &lt;adrian.hunter@nokia.com&gt;
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: warn about voltage mismatches</title>
<updated>2008-12-31T18:27:18Z</updated>
<author>
<name>David Brownell</name>
</author>
<published>2008-12-31T17:50:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f6e10b865c3ea56bdaa8c6ecfee313b997900dbb'/>
<id>urn:sha1:f6e10b865c3ea56bdaa8c6ecfee313b997900dbb</id>
<content type='text'>
Get rid of a silent failure mode when the MMC/SD host doesn't
support the voltages needed to operate a given card, by
adding a warning.  A 3.3V host and a 3.0V card, for example,
no longer need to mysteriously just not work at all.

This isn't the best diagnostic; ideally it would also tell
what voltage the card and host support (and not just by
dumping the bitmasks).

Signed-off-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: Add mmc_vddrange_to_ocrmask() helper function</title>
<updated>2008-12-31T17:18:13Z</updated>
<author>
<name>Anton Vorontsov</name>
</author>
<published>2008-11-26T19:54:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=86e8286a0e48663e1e86a5884b30a6d05de2993a'/>
<id>urn:sha1:86e8286a0e48663e1e86a5884b30a6d05de2993a</id>
<content type='text'>
This function sets the OCR mask bits according to provided voltage
ranges. Will be used by the mmc_spi OpenFirmware bindings.

Signed-off-by: Anton Vorontsov &lt;avorontsov@ru.mvista.com&gt;
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: Add 8-bit bus width support</title>
<updated>2008-12-31T17:18:12Z</updated>
<author>
<name>Jarkko Lavinen</name>
</author>
<published>2008-11-17T12:35:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b30f8af3358b5c66be223e3a9f3d11b3d02b4a8f'/>
<id>urn:sha1:b30f8af3358b5c66be223e3a9f3d11b3d02b4a8f</id>
<content type='text'>
Signed-off-by: Jarkko Lavinen &lt;jarkko.lavinen@nokia.com&gt;
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: struct device - replace bus_id with dev_name(), dev_set_name()</title>
<updated>2008-11-08T20:37:46Z</updated>
<author>
<name>Kay Sievers</name>
</author>
<published>2008-11-08T20:37:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d1b268630875a7713b5d468a0c03403c5b721c8e'/>
<id>urn:sha1:d1b268630875a7713b5d468a0c03403c5b721c8e</id>
<content type='text'>
Acked-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-Off-By: Kay Sievers &lt;kay.sievers@vrfy.org&gt;
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: increase SD write timeout for crappy cards</title>
<updated>2008-11-08T20:36:59Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2008-10-26T11:37:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=493890e75d98810a3470b4aae23be628ee5e9667'/>
<id>urn:sha1:493890e75d98810a3470b4aae23be628ee5e9667</id>
<content type='text'>
It seems that some cards are slightly out of spec and occasionally
will not be able to complete a write in the alloted 250 ms [1].
Incease the timeout slightly to allow even these cards to function
properly.

[1] http://lkml.org/lkml/2008/9/23/390

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>MMC: CSD and CID timeout values</title>
<updated>2008-10-12T09:04:37Z</updated>
<author>
<name>Matthew Fleming</name>
</author>
<published>2008-10-02T11:24:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0d3e0460f307e84904968aad6cff97bd688583d8'/>
<id>urn:sha1:0d3e0460f307e84904968aad6cff97bd688583d8</id>
<content type='text'>
The MMC spec states that the timeout for accessing the CSD and CID
registers is 64 clock cycles.

Signed-off-by: Matthew Fleming &lt;matthew.fleming@imgtec.com&gt;
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>sdio: high-speed support</title>
<updated>2008-10-12T09:04:34Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2008-08-31T15:22:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d16f57700475f670ca2828c150a34fa7102a05fc'/>
<id>urn:sha1:d16f57700475f670ca2828c150a34fa7102a05fc</id>
<content type='text'>
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>sdio: give sdio irq thread a host specific name</title>
<updated>2008-10-12T09:04:30Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2008-08-31T11:42:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6501ff604a5ae18697c9b4cd40a7738d3a68e7fe'/>
<id>urn:sha1:6501ff604a5ae18697c9b4cd40a7738d3a68e7fe</id>
<content type='text'>
There is one thread per host controller so make sure they all get
unique names.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>sdio: make sleep on error interruptable</title>
<updated>2008-10-12T09:04:28Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2008-08-31T11:38:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e633b7bcec8e26991d489a11615acf7674efbaf4'/>
<id>urn:sha1:e633b7bcec8e26991d489a11615acf7674efbaf4</id>
<content type='text'>
Make sure we can be woken from the forced sleep that is done on errors.
Removing a card often results in -ENOMEDIUM or -EILSEQ so we previously
locked up the removal process for a second.

We could completely exit on -ENOMEDIUM, but it might be a transient
glitch so treat it like any other error.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
</feed>
