<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/mmc/core/core.c, branch linux-2.6.25.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.25.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.25.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2007-11-02T07:47:06Z</updated>
<entry>
<title>cleanup asm/scatterlist.h includes</title>
<updated>2007-11-02T07:47:06Z</updated>
<author>
<name>Adrian Bunk</name>
</author>
<published>2007-10-30T09:35:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=87ae9afdcada236d0a1b38ce2c465a65916961dc'/>
<id>urn:sha1:87ae9afdcada236d0a1b38ce2c465a65916961dc</id>
<content type='text'>
Not architecture specific code should not #include &lt;asm/scatterlist.h&gt;.

This patch therefore either replaces them with
#include &lt;linux/scatterlist.h&gt; or simply removes them if they were
unused.

Signed-off-by: Adrian Bunk &lt;bunk@kernel.org&gt;
Signed-off-by: Jens Axboe &lt;jens.axboe@oracle.com&gt;
</content>
</entry>
<entry>
<title>mmc: add led trigger</title>
<updated>2007-09-24T05:15:48Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2007-09-24T05:15:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=af8350c756cb48a738474738f7bf8c0e572fa057'/>
<id>urn:sha1:af8350c756cb48a738474738f7bf8c0e572fa057</id>
<content type='text'>
Add a led trigger for each host controller that indicates if there
is a request active on the controller.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>MMC core learns about SPI</title>
<updated>2007-09-23T19:51:30Z</updated>
<author>
<name>David Brownell</name>
</author>
<published>2007-08-08T16:11:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=af51715079e7fb6b290e1881d63d815dc4de5011'/>
<id>urn:sha1:af51715079e7fb6b290e1881d63d815dc4de5011</id>
<content type='text'>
Teach the MMC/SD/SDIO core about using SPI mode.

 - Use mmc_host_is_spi() so enumeration works through SPI signaling
   and protocols, not just the native versions.

 - Provide the SPI response type flags with each request issued,
   including requests from the new lock/unlock code.

 - Understand that cmd-&gt;resp[0] and mmc_get_status() results for SPI
   return different values than for "native" MMC/SD protocol; this
   affects resetting, checking card lock status, and some others.

 - Understand that some commands act a bit differently ... notably:
     * OP_COND command doesn't return the OCR
     * APP_CMD status doesn't have an R1_APP_CMD analogue

Those changes required some new and updated primitives:

 - Provide utilities to access two SPI-only requests, and one
   request that wasn't previously needed:
     * mmc_spi_read_ocr() ... SPI only
     * mmc_spi_set_crc() ... SPI only (override by module parm)
     * mmc_send_cid() ... for use without broadcast mode

 - Updated internal routines:
     * Previous mmc_send_csd() modified into mmc_send_cxd_native();
       it uses native "R2" responses, which include 16 bytes of data.
     * Previous mmc_send_ext_csd() becomes new mmc_send_cxd_data()
       helper for command-and-data access
     * Bugfix to that mmc_send_cxd_data() code:  dma-to-stack is
       unsafe/nonportable, so kmalloc a bounce buffer instead.

 - Modified mmc_send_ext_csd() now uses mmc_send_cxd_data() helper

 - Modified mmc_send_csd(), and new mmc_spi_send_cid(), routines use
   those helper routines based on whether they're native or SPI

The newest categories of cards supported by the MMC stack aren't expected
to work yet with SPI:  MMC or SD cards with over 4GB data, and SDIO.
All those cards support SPI mode, so eventually they should work too.

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: increase power up delay</title>
<updated>2007-09-23T19:26:06Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2007-09-19T16:38:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f9996aee36921e8f1d499de1b2ea380855cf6d97'/>
<id>urn:sha1:f9996aee36921e8f1d499de1b2ea380855cf6d97</id>
<content type='text'>
Increase delay for power up in order to support some slower boards.

Also add some comments about why the delays are there.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: replace BUG_ON with WARN_ON</title>
<updated>2007-09-23T19:23:07Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2007-08-09T11:23:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d84075c8aed771d47d7ac6e96b098559da361c25'/>
<id>urn:sha1:d84075c8aed771d47d7ac6e96b098559da361c25</id>
<content type='text'>
Replace all cases of BUG_ON with WARN_ON where there is a chance
(with varying degrees of slim) that the kernel can continue without
incidence.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: fix sdio timeout calculation</title>
<updated>2007-09-23T19:16:01Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2007-08-07T12:11:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e6f918bf39773d712ab5b457bff54ade3bda0cb1'/>
<id>urn:sha1:e6f918bf39773d712ab5b457bff54ade3bda0cb1</id>
<content type='text'>
SDIO doesn't have a CSD so it uses different timeout values than
SD memory.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: fix incorrect divisor in debug output</title>
<updated>2007-09-23T19:15:45Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2007-08-07T12:06:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ce252edd869ba1fee6a9a6f83e20f349d4c4d669'/>
<id>urn:sha1:ce252edd869ba1fee6a9a6f83e20f349d4c4d669</id>
<content type='text'>
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>sdio: allow for mmc_claim_host to be aborted</title>
<updated>2007-09-23T18:55:13Z</updated>
<author>
<name>Nicolas Pitre</name>
</author>
<published>2007-06-30T14:21:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2342f3323c9a76367a1d7f9a35525ee3cb3911df'/>
<id>urn:sha1:2342f3323c9a76367a1d7f9a35525ee3cb3911df</id>
<content type='text'>
It is sometimes necessary to give up on trying to claim the host lock,
especially if that happens in a thread that has to be stopped.

While at it, fix the description for mmc_claim_host() which was wrong.

Signed-off-by: Nicolas Pitre &lt;npitre@mvista.com&gt;
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: initialize mmc subsystem with subsys_initcall()</title>
<updated>2007-09-23T18:45:39Z</updated>
<author>
<name>Nicolas Pitre</name>
</author>
<published>2007-06-16T06:07:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=26074962e8f547b96614dbe248748ba2a1996ca3'/>
<id>urn:sha1:26074962e8f547b96614dbe248748ba2a1996ca3</id>
<content type='text'>
The problem is that the sdio_bus must be registered before any SDIO
drivers are registered against it otherwise the kernel sulks.  Because
the sdio_bus registration happens through module_init (equivalent to
device_initcall), then any SDIO
drivers linked before the SDIO core code in the kernel will be initialized
first.

Upcoming SDIO function drivers are likely to be located outside the
drivers/mmc directory as it is common practice to group drivers according
to their function rather than the bus they use.  SDIO drivers are therefore
likely to appear at random location in the kernel link.

To make sure the sdio_bus is always initialized before any SDIO drivers,
let's move the MMC init to the subsys_initcall level.

Signed-off-by: Nicolas Pitre &lt;npitre@mvista.com&gt;
Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: basic SDIO device model</title>
<updated>2007-09-23T17:45:31Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2007-05-26T11:48:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e29a7d73f4277eb92aa64e17017dea33460828ef'/>
<id>urn:sha1:e29a7d73f4277eb92aa64e17017dea33460828ef</id>
<content type='text'>
Add the sdio bus type and basic device handling.

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