<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/mmc, branch v3.10.27</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/mmc?h=v3.10.27</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/mmc?h=v3.10.27'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-12-08T15:29:27Z</updated>
<entry>
<title>mmc: block: fix a bug of error handling in MMC driver</title>
<updated>2013-12-08T15:29:27Z</updated>
<author>
<name>KOBAYASHI Yoshitake</name>
<email>yoshitake.kobayashi@toshiba.co.jp</email>
</author>
<published>2013-07-06T22:35:45Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=604ae797e7cd1eca7897eac555961a5a25a9bde5'/>
<id>urn:sha1:604ae797e7cd1eca7897eac555961a5a25a9bde5</id>
<content type='text'>
commit c8760069627ad3b0dbbea170f0c4c58b16e18d3d upstream.

Current MMC driver doesn't handle generic error (bit19 of device
status) in write sequence. As a result, write data gets lost when
generic error occurs. For example, a generic error when updating a
filesystem management information causes a loss of write data and
corrupts the filesystem. In the worst case, the system will never
boot.

This patch includes the following functionality:
  1. To enable error checking for the response of CMD12 and CMD13
     in write command sequence
  2. To retry write sequence when a generic error occurs

Messages are added for v2 to show what occurs.

Signed-off-by: KOBAYASHI Yoshitake &lt;yoshitake.kobayashi@toshiba.co.jp&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>mmc: atmel-mci: fix oops in atmci_tasklet_func</title>
<updated>2013-12-04T18:56:40Z</updated>
<author>
<name>Rodolfo Giometti</name>
<email>giometti@enneenne.com</email>
</author>
<published>2013-09-09T15:31:59Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=63a23e393fed93ca823f7c7fc415795e2ffe7670'/>
<id>urn:sha1:63a23e393fed93ca823f7c7fc415795e2ffe7670</id>
<content type='text'>
commit fbd986cd420d1deeabf1039ec4e74075a5639db5 upstream.

In some cases, a NULL pointer dereference happens because data is NULL when
STATE_END_REQUEST case is reached in atmci_tasklet_func.

Signed-off-by: Rodolfo Giometti &lt;giometti@enneenne.com&gt;
Acked-by: Ludovic Desroches &lt;ludovic.desroches@atmel.com&gt;
Acked-by: Nicolas Ferre &lt;nicolas.ferre@atmel.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>mmc: atmel-mci: abort transfer on timeout error</title>
<updated>2013-12-04T18:56:39Z</updated>
<author>
<name>Ludovic Desroches</name>
<email>ludovic.desroches@atmel.com</email>
</author>
<published>2013-09-09T15:29:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6edfd0331f788a5d62736c6a422488708175b4c4'/>
<id>urn:sha1:6edfd0331f788a5d62736c6a422488708175b4c4</id>
<content type='text'>
commit c1fa3426aa5c782724c97394303d52228206eda4 upstream.

When a software timeout occurs, the transfer is not stopped. In DMA case,
it causes DMA channel to be stuck because the transfer is still active
causing following transfers to be queued but not computed.

Signed-off-by: Ludovic Desroches &lt;ludovic.desroches@atmel.com&gt;
Reported-by: Alexander Morozov &lt;etesial@gmail.com&gt;
Acked-by: Nicolas Ferre &lt;nicolas.ferre@atmel.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>mmc: tmio_mmc_dma: fix PIO fallback on SDHI</title>
<updated>2013-09-27T00:18:29Z</updated>
<author>
<name>Sergei Shtylyov</name>
<email>sergei.shtylyov@cogentembedded.com</email>
</author>
<published>2013-08-25T03:38:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c0da08882ef2c738edacd5e7fbca671e663f9951'/>
<id>urn:sha1:c0da08882ef2c738edacd5e7fbca671e663f9951</id>
<content type='text'>
commit f936f9b67b7f8c2eae01dd303a0e90bd777c4679 upstream.

I'm testing SH-Mobile SDHI driver in DMA mode with  a new DMA controller  using
'bonnie++' and getting DMA error after which the tmio_mmc_dma.c code falls back
to PIO but all commands time out after that.  It turned out that the fallback
code calls tmio_mmc_enable_dma() with RX/TX channels already freed and pointers
to them cleared, so that the function bails out early instead  of clearing the
DMA bit in the CTL_DMA_ENABLE register. The regression was introduced by commit
162f43e31c5a376ec16336e5d0ac973373d54c89 (mmc: tmio: fix a deadlock).
Moving tmio_mmc_enable_dma() calls to the top of the PIO fallback code in
tmio_mmc_start_dma_{rx|tx}() helps.

Signed-off-by: Sergei Shtylyov &lt;sergei.shtylyov@cogentembedded.com&gt;
Acked-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>mmc: omap_hsmmc: Skip platform_get_resource_byname() for dt case</title>
<updated>2013-05-26T18:23:11Z</updated>
<author>
<name>Santosh Shilimkar</name>
<email>santosh.shilimkar@ti.com</email>
</author>
<published>2013-05-10T12:12:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4a29b5591faf25555fdf2b717594d50f70c15066'/>
<id>urn:sha1:4a29b5591faf25555fdf2b717594d50f70c15066</id>
<content type='text'>
MMC driver probe will abort for DT case because of failed
platform_get_resource_byname() lookup. Fix it by skipping resource
lookup byname for device tree build.

Issue is hidden because hwmod populates the IO resources which
helps to succeed platform_get_resource_byname() and probe.

Signed-off-by: Santosh Shilimkar &lt;santosh.shilimkar@ti.com&gt;
Signed-off-by: Balaji T K &lt;balajitk@ti.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: omap_hsmmc: convert to dma_request_slave_channel_compat</title>
<updated>2013-05-26T18:23:10Z</updated>
<author>
<name>Matt Porter</name>
<email>mporter@ti.com</email>
</author>
<published>2013-05-10T12:12:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d272fbf0ca4a59339c768d76858f4add6ff36ace'/>
<id>urn:sha1:d272fbf0ca4a59339c768d76858f4add6ff36ace</id>
<content type='text'>
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports platforms booting
with or without DT populated.

Signed-off-by: Matt Porter &lt;mporter@ti.com&gt;
Acked-by: Tony Lindgren &lt;tony@atomide.com&gt;
Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Balaji T K &lt;balajitk@ti.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: omap_hsmmc: Fix the DT pbias workaround for MMC controllers 2 to 5</title>
<updated>2013-05-26T18:23:09Z</updated>
<author>
<name>Tony Lindgren</name>
<email>tony@atomide.com</email>
</author>
<published>2013-05-10T12:12:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cf5ae40b3968ca769e683b9b071685ad82ee893c'/>
<id>urn:sha1:cf5ae40b3968ca769e683b9b071685ad82ee893c</id>
<content type='text'>
Otherwise SDIO cards won't necessarily work when booted with
device tree as we will never power down the SDIO cards. This
means the SDIO card reset does not happen which at least some
WLAN controllers expect to happen with ifconfig wlan0 down.

The PBIAS voltage is only available for the first controller
instance, so let's limit the PBIAS workaround to the first
controller only.

Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Tested-by: Luciano Coelho &lt;coelho@ti.com&gt;
Signed-off-by: Balaji T K &lt;balajitk@ti.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdhci-pci: add more device ids</title>
<updated>2013-05-26T17:50:50Z</updated>
<author>
<name>Adrian Hunter</name>
<email>adrian.hunter@intel.com</email>
</author>
<published>2013-04-26T08:27:23Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=728ef3d1939e23e26067608d8d8da9571be14b1d'/>
<id>urn:sha1:728ef3d1939e23e26067608d8d8da9571be14b1d</id>
<content type='text'>
Add three more PCI device ids.

Signed-off-by: Adrian Hunter &lt;adrian.hunter@intel.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdhci-acpi: add more device ids</title>
<updated>2013-05-26T17:50:50Z</updated>
<author>
<name>Adrian Hunter</name>
<email>adrian.hunter@intel.com</email>
</author>
<published>2013-04-26T08:27:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=07a588837be0a18075fedf71e6963b5109abec03'/>
<id>urn:sha1:07a588837be0a18075fedf71e6963b5109abec03</id>
<content type='text'>
Add three more ACPI HIDs.  Also, as some devices must be
further distinguished by ACPI UID, slot information is now
associated with HID and UID.

Signed-off-by: Adrian Hunter &lt;adrian.hunter@intel.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdhci-acpi: fix initial runtime pm status</title>
<updated>2013-05-26T17:50:49Z</updated>
<author>
<name>Adrian Hunter</name>
<email>adrian.hunter@intel.com</email>
</author>
<published>2013-04-26T08:27:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1d1ff45871984364056ebfc528ed31ff7f03f970'/>
<id>urn:sha1:1d1ff45871984364056ebfc528ed31ff7f03f970</id>
<content type='text'>
Initial runtime pm status is active.

Signed-off-by: Adrian Hunter &lt;adrian.hunter@intel.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
</feed>
