<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/mmc, branch v3.4.2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/mmc?h=v3.4.2</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/mmc?h=v3.4.2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-06-01T07:18:27Z</updated>
<entry>
<title>mmc: omap_hsmmc: pass IRQF_ONESHOT to request_threaded_irq</title>
<updated>2012-06-01T07:18:27Z</updated>
<author>
<name>Ming Lei</name>
<email>ming.lei@canonical.com</email>
</author>
<published>2012-05-17T02:27:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e5bdf9b518d0ff03455dce3da9bce8ad95c25e6d'/>
<id>urn:sha1:e5bdf9b518d0ff03455dce3da9bce8ad95c25e6d</id>
<content type='text'>
commit db35f83ef47b5f180f2670d11f5f93992314ea09 upstream.

The flag of IRQF_ONESHOT should be passed to request_threaded_irq,
otherwise the following failure message should be dumped because
hardware handler is defined as NULL:

[    3.383483] genirq: Threaded irq requested with handler=NULL and
!ONESHOT for irq 368
[    3.392730] omap_hsmmc: probe of omap_hsmmc.0 failed with error -22

The patch fixes one kernel hang bug which is caused by mmc card
probe failure and root device can't be brought up.

Signed-off-by: Ming Lei &lt;ming.lei@canonical.com&gt;
Acked-by: Venkatraman S &lt;svenkatr@ti.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: cd-gpio: protect against NULL context in mmc_cd_gpio_free()</title>
<updated>2012-06-01T07:18:27Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2012-04-24T15:56:29Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6cd4efb3a17356075c8e3f1bd191b4d120714851'/>
<id>urn:sha1:6cd4efb3a17356075c8e3f1bd191b4d120714851</id>
<content type='text'>
commit 0e9f480bb553d39ee06ccd45639ba7a5446a7b81 upstream.

Do not oops, even if mmc_cd_gpio_free() is mistakenly called on a driver
cleanup path, even though a previous call to mmc_cd_gpio_request() failed.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
[stable@: please apply to 3.3-stable]
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: sdio: avoid spurious calls to interrupt handlers</title>
<updated>2012-06-01T07:18:26Z</updated>
<author>
<name>Nicolas Pitre</name>
<email>nicolas.pitre@linaro.org</email>
</author>
<published>2012-04-16T23:16:54Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=11c8c735ebf68c754bdd94cebd307a96fcd95068'/>
<id>urn:sha1:11c8c735ebf68c754bdd94cebd307a96fcd95068</id>
<content type='text'>
commit bbbc4c4d8c5face097d695f9bf3a39647ba6b7e7 upstream.

Commit 06e8935feb ("optimized SDIO IRQ handling for single irq")
introduced some spurious calls to SDIO function interrupt handlers,
such as when the SDIO IRQ thread is started, or the safety check
performed upon a system resume.  Let's add a flag to perform the
optimization only when a real interrupt is signaled by the host
driver and we know there is no point confirming it.

Reported-by: Sujit Reddy Thumma &lt;sthumma@codeaurora.org&gt;
Signed-off-by: Nicolas Pitre &lt;nico@linaro.org&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>Merge branch 'fixes' of git://git.infradead.org/users/vkoul/slave-dma</title>
<updated>2012-04-26T22:33:36Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-04-26T22:33:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=acdf2fc860f785781bb304a7f178141541f85283'/>
<id>urn:sha1:acdf2fc860f785781bb304a7f178141541f85283</id>
<content type='text'>
Pull [GIT PULL] slave-dmaengine fixes from Vinod Koul.

* 'fixes' of git://git.infradead.org/users/vkoul/slave-dma:
  dmaengine/amba-pl08x : reset phychan_hold on terminate all
  dma: pl330: fix a couple of compilation warnings
  dma/ste_dma40: fix erroneous comparison
  dma/ste_dma40: explicitly include regulator consumer header
  dma40: Improve the logic of stopping logical chan
  dmaengine: at_hdmac: remove clear-on-read in atc_dostart()
  dma: mxs-dma: enable channel in device_issue_pending call
  dmaengine: imx-dma: dont complete descriptor for cyclic dma
</content>
</entry>
<entry>
<title>mmc: core: Do not pre-claim host in suspend</title>
<updated>2012-04-21T01:52:13Z</updated>
<author>
<name>Ulf Hansson</name>
<email>ulf.hansson@stericsson.com</email>
</author>
<published>2012-04-19T09:55:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7c5709194096beea1ab6e6db46768d70a068efb0'/>
<id>urn:sha1:7c5709194096beea1ab6e6db46768d70a068efb0</id>
<content type='text'>
Since SDIO drivers may want to do some SDIO operations in their suspend
callback functions, we must not keep the host claimed when calling them.

Daniel Drake reported that libertas_sdio encountered a deadlock in its
suspend function.

Signed-off-by: Ulf Hansson &lt;ulf.hansson@stericsson.com&gt;
Tested-by: Daniel Drake &lt;dsd@laptop.org&gt;
[stable@: please apply to 3.2-stable and 3.3-stable]
Cc: stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: dw_mmc: prevent NULL dereference for dma_ops</title>
<updated>2012-04-21T01:52:05Z</updated>
<author>
<name>Jaehoon Chung</name>
<email>jh80.chung@samsung.com</email>
</author>
<published>2012-04-18T06:42:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e1631f989e0c6c8d9b43a2dbdd1097f70da603a5'/>
<id>urn:sha1:e1631f989e0c6c8d9b43a2dbdd1097f70da603a5</id>
<content type='text'>
Now, dma_ops is assumed that use the IDMAC.  But if dma_ops is assigned
the pdata-&gt;dma_ops, we didn't ensure that callback function is defined.

If the callback isn't defined, then we should run in PIO mode.

Signed-off-by: Jaehoon Chung &lt;jh80.chung@samsung.com&gt;
Signed-off-by: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;
Acked-by: Will Newton &lt;will.newton@imgtec.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: unbreak sdhci-esdhc-imx on i.MX25</title>
<updated>2012-04-21T00:45:00Z</updated>
<author>
<name>Eric Bénard</name>
<email>eric@eukrea.com</email>
</author>
<published>2012-04-18T00:30:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b89152824f993a9572b47eb31f4579feadeac34c'/>
<id>urn:sha1:b89152824f993a9572b47eb31f4579feadeac34c</id>
<content type='text'>
This was broken by me in 37865fe91582582a6f6c00652f6a2b1ff71f8a78
("mmc: sdhci-esdhc-imx: fix timeout on i.MX's sdhci") where more
extensive tests would have shown that read or write of data to the
card were failing (even if the partition table was correctly read).

Signed-off-by: Eric Bénard &lt;eric@eukrea.com&gt;
Acked-by: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Cc: stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: cd-gpio: Include header to pickup exported symbol prototypes</title>
<updated>2012-04-21T00:45:00Z</updated>
<author>
<name>H Hartley Sweeten</name>
<email>hartleys@visionengravers.com</email>
</author>
<published>2012-04-17T20:03:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5ca6518832ac913ac277b50ceddda8372dbf7bea'/>
<id>urn:sha1:5ca6518832ac913ac277b50ceddda8372dbf7bea</id>
<content type='text'>
Include the linux/mmc/cd-gpio.h header to pickup the prototypes
for the two exported symbols.

This quiets the sparse warnings:

warning: symbol 'mmc_cd_gpio_request' was not declared. Should it be static?
warning: symbol 'mmc_cd_gpio_free' was not declared. Should it be static?

Signed-off-by: H Hartley Sweeten &lt;hsweeten@visionengravers.com&gt;
Acked-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Acked-by: Venkatraman S &lt;svenkatr@ti.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdhci: refine non-removable card checking for card detection</title>
<updated>2012-04-21T00:44:25Z</updated>
<author>
<name>Daniel Drake</name>
<email>dsd@laptop.org</email>
</author>
<published>2012-04-09T23:14:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=87b87a3fc0eec58d95e4216392f889a26439ad22'/>
<id>urn:sha1:87b87a3fc0eec58d95e4216392f889a26439ad22</id>
<content type='text'>
Commit c79396c191bc19 ("mmc: sdhci: prevent card detection activity
for non-removable cards") disables card detection where the cards
are marked as non-removable.

This makes sense, but the implementation detail of calling
mmc_card_is_removable() causes some problems, because
mmc_card_is_removable() is overloaded with CONFIG_MMC_UNSAFE_RESUME
semantics.

In the OLPC XO case, we need CONFIG_MMC_UNSAFE_RESUME because our root
filesystem is stored on SD, but we also have external SD card slots
where we want automatic card detection.

Refine the check to only apply to hosts marked as MMC_CAP_NONREMOVABLE,
which is defined to mean that the card is *really* nonremovable. This
could be revisited in future if we find a way to improve
CONFIG_MMC_UNSAFE_RESUME semantics.

Signed-off-by: Daniel Drake &lt;dsd@laptop.org&gt;
Acked-by: Chuanxiao Dong &lt;chuanxiao.dong@intel.com&gt;
[stable@: please apply to 3.3-stable]
Cc: stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: dw_mmc: Fix switch from DMA to PIO</title>
<updated>2012-04-21T00:30:37Z</updated>
<author>
<name>Seungwon Jeon</name>
<email>tgih.jun@samsung.com</email>
</author>
<published>2012-04-10T00:53:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a99aa9b9b4f4f3e496d17a1b4e0ff63fb0c9f31d'/>
<id>urn:sha1:a99aa9b9b4f4f3e496d17a1b4e0ff63fb0c9f31d</id>
<content type='text'>
When dw_mci_pre_dma_transfer returns failure in some reasons,
dw_mci_submit_data will prepare to switch the PIO mode from DMA.
After switching to PIO mode, DMA(IDMAC in particular) is still
enabled. This makes the corruption in handling interrupt and
the driver lock-up.

Signed-off-by: Seungwon Jeon &lt;tgih.jun@samsung.com&gt;
Acked-by: Will Newton &lt;will.newton@imgtec.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
</feed>
