<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/mmc/core, branch v3.8.2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/mmc/core?h=v3.8.2</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/mmc/core?h=v3.8.2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-02-28T13:38:40Z</updated>
<entry>
<title>mmc: core: expose RPMB partition only for CMD23 capable hosts</title>
<updated>2013-02-28T13:38:40Z</updated>
<author>
<name>Balaji T K</name>
<email>balajitk@ti.com</email>
</author>
<published>2013-01-25T11:30:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2c3c78916a91b01d0571fbc1ae7434ca3c2d2288'/>
<id>urn:sha1:2c3c78916a91b01d0571fbc1ae7434ca3c2d2288</id>
<content type='text'>
commit d0123ccac55088811bde4f76c4a3fdbd39c3cfba upstream.

SET_BLOCK_COUNT CMD23 is needed for all access to RPMB partition.  If
block count is not set by CMD23, all subsequent read/write commands fail
as per eMMC specification. So, If the host does not support CMD23, do not
expose RPMB partition.

Accessing RPMB partition can cause hang / huge delay for hosts which do
not support CMD23.

Signed-off-by: Balaji T K &lt;balajitk@ti.com&gt;
Reported-and-Tested-by: Peter Ujfalusi &lt;peter.ujfalusi@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: extend the slot-gpio card-detection to use host's .card_event() method</title>
<updated>2012-12-07T18:55:50Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2012-12-04T15:51:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=451c89578eb4791b9d329eb71a79e6715e60f89e'/>
<id>urn:sha1:451c89578eb4791b9d329eb71a79e6715e60f89e</id>
<content type='text'>
The slot-gpio API provides a generic card-detection handler. To support a
wider range of hosts it has to call the host's card-event callback, if
implemented. Also increase the debounce interval to 200ms to match the
SDHCI driver.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Reviewed-by: Shawn Guo &lt;shawn.guo@linaro.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: Limit MMC speed to 52MHz if not HS200</title>
<updated>2012-12-06T18:55:11Z</updated>
<author>
<name>Al Cooper</name>
<email>alcooperx@gmail.com</email>
</author>
<published>2012-11-30T15:53:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ccb52a00fd3fdea428e29816cbacb0a78090d474'/>
<id>urn:sha1:ccb52a00fd3fdea428e29816cbacb0a78090d474</id>
<content type='text'>
If "caps2" host capabilities does not indicate support for MMC
HS200, don't allow clock speeds &gt;52MHz. Currently, for MMC, the
clock speed is set to the lesser of the max speed the eMMC module
supports (card-&gt;ext_csd.hs_max_dtr) or the max base clock of the
host controller (host-&gt;f_max based on BASE_CLK_FREQ in the host
CAPS register). This means that a host controller that doesn't
support HS200 mode but has a base clock of 100MHz and an eMMC module
that supports HS200 speeds will end up using a 100MHz clock.

Signed-off-by: Al Cooper &lt;alcooperx@gmail.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: Remove redundant null check before kfree in bus.c</title>
<updated>2012-12-06T18:55:07Z</updated>
<author>
<name>Sachin Kamat</name>
<email>sachin.kamat@linaro.org</email>
</author>
<published>2012-11-20T09:13:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8db580ccfd3b3aa0f7d800d2db4e8c32e7da2cda'/>
<id>urn:sha1:8db580ccfd3b3aa0f7d800d2db4e8c32e7da2cda</id>
<content type='text'>
kfree on a null pointer is a no-op.

Signed-off-by: Sachin Kamat &lt;sachin.kamat@linaro.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: Remove redundant null check before kfree in sdio_bus.c</title>
<updated>2012-12-06T18:55:06Z</updated>
<author>
<name>Sachin Kamat</name>
<email>sachin.kamat@linaro.org</email>
</author>
<published>2012-11-20T09:13:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4c42d6cc245e8d41eb83c724cf38cdb9342ea5ba'/>
<id>urn:sha1:4c42d6cc245e8d41eb83c724cf38cdb9342ea5ba</id>
<content type='text'>
kfree on a null pointer is a no-op.

Signed-off-by: Sachin Kamat &lt;sachin.kamat@linaro.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdio: Add empty bus-level suspend/resume callbacks</title>
<updated>2012-12-06T18:55:04Z</updated>
<author>
<name>Rafael J. Wysocki</name>
<email>rjw@sisk.pl</email>
</author>
<published>2012-12-02T13:48:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b0afd8f68adf6a9b671b0420ab9116a36409ef7f'/>
<id>urn:sha1:b0afd8f68adf6a9b671b0420ab9116a36409ef7f</id>
<content type='text'>
Suspend methods provided by SDIO drivers are not supposed to be called by
the PM core.  Instead, when the SDIO core gets to suspend a device's
ancestor, it calls the device driver's suspend routine.  However, the PM
core executes suspend callback routines directly for device drivers whose
bus types don't provide suspend callbacks.  In consequece, because the
SDIO bus type doesn't provide a suspend callback, the SDIO drivers'
suspend routines will be executed by the PM core (which shouldn't
happen).

To prevent this from happening, add empty system suspend/resume callbacks
for the SDIO bus type.

An analogous change had been made already by commit (e841a7c mmc: sdio:
Use empty system suspend/resume callbacks at the bus level), but then it
was reverted inadvertently by commit (d8e2ac3 mmc: sdio: Fix PM_SLEEP
related build warnings) that attempted to fix build warnings introduced
by commit e841a7c.

Reported-by: NeilBrown &lt;neilb@suse.de&gt;
Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: core: Add mmc_set_blockcount feature</title>
<updated>2012-12-06T18:54:48Z</updated>
<author>
<name>Loic Pallardy</name>
<email>loic.pallardy-ext@stericsson.com</email>
</author>
<published>2012-08-06T15:12:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=67c79db8d9c0e5d2e2075c9108f42566ce0f8a6f'/>
<id>urn:sha1:67c79db8d9c0e5d2e2075c9108f42566ce0f8a6f</id>
<content type='text'>
Provide support for automatically sending Set Block Count
(CMD23) messages. Used at least for RPMB support.

Signed-off-by: Alex Macro &lt;alex.macro@stericsson.com&gt;
Signed-off-by: Loic Pallardy &lt;loic.pallardy@stericsson.com&gt;
Reviewed-by: Namjae Jeon &lt;linkinjeon@gmail.com&gt;
Acked-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Acked-by: Johan Rudholm &lt;johan.rudholm@stericsson.com&gt;
Acked-by: Krishna Konda &lt;kkonda@codeaurora.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: core: Extend sysfs to ext_csd parameters for RPMB support</title>
<updated>2012-12-06T18:54:48Z</updated>
<author>
<name>Loic Pallardy</name>
<email>loic.pallardy-ext@stericsson.com</email>
</author>
<published>2012-08-06T15:12:29Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=188cc0424e9bd7733ee3e412da6df2cf42701061'/>
<id>urn:sha1:188cc0424e9bd7733ee3e412da6df2cf42701061</id>
<content type='text'>
Extend current sysfs access to ext_csd rpmb parameters (RPMB partition
size) and rel_sector information.

Signed-off-by: Loic Pallardy &lt;loic.pallardy@stericsson.com&gt;
Reviewed-by: Namjae Jeon &lt;linkinjeon@gmail.com&gt;
Acked-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Acked-by: Johan Rudholm &lt;johan.rudholm@stericsson.com&gt;
Acked-by: Krishna Konda &lt;kkonda@codeaurora.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: core: Expose access to RPMB partition</title>
<updated>2012-12-06T18:54:46Z</updated>
<author>
<name>Loic Pallardy</name>
<email>loic.pallardy-ext@stericsson.com</email>
</author>
<published>2012-11-17T23:08:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=090d25fe224c0933d2b261aad91532e725c1d889'/>
<id>urn:sha1:090d25fe224c0933d2b261aad91532e725c1d889</id>
<content type='text'>
Following JEDEC standard, if the mmc supports RPMB partition,
a new interface is created and exposed via /dev/block.
Users will be able to access RPMB partition using standard
mmc IOCTL commands.

Signed-off-by: Alex Macro &lt;alex.macro@stericsson.com&gt;
Signed-off-by: Loic Pallardy &lt;loic.pallardy@stericsson.com&gt;
Reviewed-by: Namjae Jeon &lt;linkinjeon@gmail.com&gt;
Acked-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Acked-by: Johan Rudholm &lt;johan.rudholm@stericsson.com&gt;
Acked-by: Krishna Konda &lt;kkonda@codeaurora.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: Standardise capability type</title>
<updated>2012-12-06T18:54:44Z</updated>
<author>
<name>Lee Jones</name>
<email>lee.jones@linaro.org</email>
</author>
<published>2012-11-14T12:35:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5f1a4dd0372038f2490afa4540cd66b8d092839e'/>
<id>urn:sha1:5f1a4dd0372038f2490afa4540cd66b8d092839e</id>
<content type='text'>
There are discrepancies with regards to how MMC capabilities
are carried throughout the subsystem. Let's standardise them
to eliminate any confusion.

Signed-off-by: Lee Jones &lt;lee.jones@linaro.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
</feed>
