<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/include/linux/mmc/host.h, branch linux-2.6.22.y</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.22.y</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.22.y'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2007-05-01T12:14:50+00:00</updated>
<entry>
<title>MMC: Fix handling of low-voltage cards</title>
<updated>2007-05-01T12:14:50+00:00</updated>
<author>
<name>Philip Langdale</name>
<email>philipl@overt.org</email>
</author>
<published>2007-03-17T02:39:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=55556da01284af8c2174b786b3eca8e11301b656'/>
<id>urn:sha1:55556da01284af8c2174b786b3eca8e11301b656</id>
<content type='text'>
Fix handling of low voltage MMC cards.

The latest MMC and SD specs both agree that support for
low-voltage operations is indicated by bit 7 in the OCR.
The MMC spec states that the low voltage range is
1.65-1.95V while the SD spec leaves the actual voltage
range undefined - meaning that there is still no such
thing as a low voltage SD card.

However, an old Sandisk spec implied that bits 7.0
represented voltages below 2.0V in 1V or 0.5V increments,
and the code was accordingly written with that expectation.

This confusion meant that host drivers attempting to support
the typical low voltage (1.8V) would set the wrong bits in
the host OCR mask (usually bits 5 and/or 6) resulting in the
the low voltage mode never being used.

This change corrects the low voltage range and adds sanity
checks on the reserved bits (0-6) and for SD cards that
claim to support low-voltage operations.

Signed-off-by: Philip Langdale &lt;philipl@overt.org&gt;
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>MMC: Consolidate voltage definitions</title>
<updated>2007-05-01T11:42:28+00:00</updated>
<author>
<name>Philip Langdale</name>
<email>philipl@overt.org</email>
</author>
<published>2007-03-12T00:15:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=4be34c99a2f3aa90fa42e62c0918f07afb8a645b'/>
<id>urn:sha1:4be34c99a2f3aa90fa42e62c0918f07afb8a645b</id>
<content type='text'>
Consolidate the list of available voltages.

Up until now, a separate set of defines has been
used for host-&gt;vdd than that used for the OCR
voltage mask values. Having two sets of defines
allows them to get out of sync and the current
sets are already inconsistent with one claiming
to describe ranges and the other specific voltages.

Only the SDHCI driver uses the host-&gt;vdd defines and
it is easily fixed to use the OCR defines.

Signed-off-by: Philip Langdale &lt;philipl@overt.org&gt;
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: add bus handler</title>
<updated>2007-05-01T11:41:06+00:00</updated>
<author>
<name>Pierre Ossman</name>
<email>drzeus@drzeus.cx</email>
</author>
<published>2006-12-30T23:11:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=7ea239d9e6d6993469a6a8ca83ff23834dfc3fce'/>
<id>urn:sha1:7ea239d9e6d6993469a6a8ca83ff23834dfc3fce</id>
<content type='text'>
Delegate protocol handling to "bus handlers". This allows the core to
just handle the task of arbitrating the bus. Initialisation and
pampering of cards is now done by the different bus handlers.

This design also allows MMC and SD (and later SDIO) to be more cleanly
separated, allowing easier maintenance.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: Move core functions to subdir</title>
<updated>2007-05-01T11:04:18+00:00</updated>
<author>
<name>Pierre Ossman</name>
<email>drzeus@drzeus.cx</email>
</author>
<published>2007-02-28T14:33:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=aaac1b470bd0dccb30912356617069dc6199cc80'/>
<id>urn:sha1:aaac1b470bd0dccb30912356617069dc6199cc80</id>
<content type='text'>
Create a "core" subdirectory to house the central bus handling
functions.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: deprecate mmc bus topology</title>
<updated>2007-05-01T11:04:18+00:00</updated>
<author>
<name>Pierre Ossman</name>
<email>drzeus@drzeus.cx</email>
</author>
<published>2007-01-03T18:47:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=b855885e3b60cf6f9452848712a62517b94583eb'/>
<id>urn:sha1:b855885e3b60cf6f9452848712a62517b94583eb</id>
<content type='text'>
The classic MMC bus was defined as multi card bus
system, which is reflected in the design in the MMC
layer.

When SD showed up, the bus topology was abandoned
and a star topology (one card per host) was mandated.
MMC version 4 has followed this, officially deprecating
the bus topology.

As we do not have any known users of the bus
topology we can remove support for it. This will
simplify the code and rectify some incorrect
assumptions in the newer additions.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: Flush pending detects on host removal</title>
<updated>2007-05-01T11:04:17+00:00</updated>
<author>
<name>Pierre Ossman</name>
<email>drzeus@drzeus.cx</email>
</author>
<published>2007-02-11T19:43:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=3b91e5507cddaca53bccf1524ff11a0ac5c85531'/>
<id>urn:sha1:3b91e5507cddaca53bccf1524ff11a0ac5c85531</id>
<content type='text'>
Make sure we kill of any pending detection runs when the host
is removed instead of when it is freed. Also add some debugging
to make sure the driver doesn't queue up more detection after it
has removed the host.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: Move OCR bit defines</title>
<updated>2007-05-01T11:04:16+00:00</updated>
<author>
<name>Pierre Ossman</name>
<email>drzeus@drzeus.cx</email>
</author>
<published>2007-02-09T21:49:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=f74d132cec60b686bce1f284822c1a496700bd3c'/>
<id>urn:sha1:f74d132cec60b686bce1f284822c1a496700bd3c</id>
<content type='text'>
All host drivers were #include:ing mmc/protocol.h just to
get access to the OCR bit defines. Move these to host.h instead.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: require explicit support for high-speed</title>
<updated>2007-03-06T12:26:55+00:00</updated>
<author>
<name>Pierre Ossman</name>
<email>drzeus@drzeus.cx</email>
</author>
<published>2007-02-18T11:07:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=cd9277c011a99769fa371521b460ed57f6d280b1'/>
<id>urn:sha1:cd9277c011a99769fa371521b460ed57f6d280b1</id>
<content type='text'>
The new high-speed timings are similar to each other and the old
system, but not identical. And although things "just work" most of
the time, sometimes it does not. So we need to start marking which
hosts are known to fully comply with the new timings.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: Allow host drivers to specify max block count</title>
<updated>2007-02-04T19:54:10+00:00</updated>
<author>
<name>Pierre Ossman</name>
<email>drzeus@drzeus.cx</email>
</author>
<published>2006-11-21T16:55:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=55db890a838c7b37256241b1fc53d6344aa79cc0'/>
<id>urn:sha1:55db890a838c7b37256241b1fc53d6344aa79cc0</id>
<content type='text'>
Many controllers have an upper limit on the number of blocks that can be
transferred in one request. Allow the host drivers to specify this and make
sure we avoid hitting this limit.

Also change the max_sectors field to avoid confusion. This makes it map
less directly to the block layer limits, but as they didn't apply directly
on MMC cards anyway, this isn't a great loss.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: Allow host drivers to specify a max block size</title>
<updated>2007-02-04T19:54:10+00:00</updated>
<author>
<name>Pierre Ossman</name>
<email>drzeus@drzeus.cx</email>
</author>
<published>2006-11-21T16:54:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=fe4a3c7a20f14d86022a8132adbf6ddb98e7197c'/>
<id>urn:sha1:fe4a3c7a20f14d86022a8132adbf6ddb98e7197c</id>
<content type='text'>
Most controllers have an upper limit on the block size. Allow the host
drivers to specify this and make sure we avoid hitting this limit.

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