<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/mmc/core, branch v3.6.2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/mmc/core?h=v3.6.2</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/mmc/core?h=v3.6.2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-10-12T20:50:34Z</updated>
<entry>
<title>mmc: slot-gpio: Fix missing assignment to ctx-&gt;ro_gpio</title>
<updated>2012-10-12T20:50:34Z</updated>
<author>
<name>Chris Ball</name>
<email>cjb@laptop.org</email>
</author>
<published>2012-09-10T02:56:48Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=25356be596603e72329799728cbe494652ccdaab'/>
<id>urn:sha1:25356be596603e72329799728cbe494652ccdaab</id>
<content type='text'>
commit 15e8a8e42966162c207bb97ed55c803bc437eeae upstream.

mmc_gpio_request_ro() doesn't store the requested gpio in ctx-&gt;ro_gpio.
As a result, subsequent calls to mmc_gpio_get_ro() will always fail
with -ENOSYS because the gpio number isn't available to that function.

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: core: reset signal voltage on power up</title>
<updated>2012-07-22T19:25:53Z</updated>
<author>
<name>Aaron Lu</name>
<email>aaron.lu@amd.com</email>
</author>
<published>2012-07-10T08:55:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=108ecc4cf9c46a4caabaf18efc42d19818c95b70'/>
<id>urn:sha1:108ecc4cf9c46a4caabaf18efc42d19818c95b70</id>
<content type='text'>
Add a call to mmc_set_signal_voltage() to set signal voltage to 3.3v in
mmc_power_up so that we do not need to touch signal voltage setting in
mmc/sd/sdio init functions and rescan function.

For mmc/sd cards, when doing a suspend/resume cycle, consider the unsafe
resume case, the card will lose its power and when powered on again, we
will set signal voltage to 3.3v in mmc_power_up before its resume function
gets called, which will re-init the card.

And for sdio cards, when doing a suspend/resume cycle, consider the unsafe
resume case, the card will either lose its power or not depending on if it
wants to wakeup the host. If power is not maintained, it is the same case as
mmc/sd cards. If power is maintained, mmc_power_up will not be called and
the card's signal voltage will remain at the last setting.

Signed-off-by: Aaron Lu &lt;aaron.lu@amd.com&gt;
Tested-by: Venkatraman S &lt;svenkatr@ti.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sd: Fix sd current limit setting</title>
<updated>2012-07-22T19:25:52Z</updated>
<author>
<name>Aaron Lu</name>
<email>aaron.lu@amd.com</email>
</author>
<published>2012-07-04T05:31:48Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=55c4665ea0a42fd6427826bfce96eb4b0389262a'/>
<id>urn:sha1:55c4665ea0a42fd6427826bfce96eb4b0389262a</id>
<content type='text'>
Host has different current capabilities at different voltages, we need
to record these settings seperately. The defined voltages are 1.8/3.0/3.3.
For other voltages, we do not touch current limit setting.

Before we set the current limit for the sd card, find out the host's
operating voltage first and then find out the current capabilities of
the host at that voltage to set the current limit.

Signed-off-by: Aaron Lu &lt;aaron.lu@amd.com&gt;
Reviewed-by: Philip Rakity &lt;prakity@marvell.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdio: Change pr_warning to pr_warn_ratelimited</title>
<updated>2012-07-22T19:25:48Z</updated>
<author>
<name>Liu Chuansheng</name>
<email>chuansheng.liu@intel.com</email>
</author>
<published>2012-07-09T10:26:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=aa6439daddf579b93ace8b45956a416234c3854c'/>
<id>urn:sha1:aa6439daddf579b93ace8b45956a416234c3854c</id>
<content type='text'>
When debugging one bad issue, got lots of pr_warning messages
"queuing unknown CIS tuple" which caused a printk storm and
flooded the console.

This patch changes the pr_warning to use pr_warn_ratelimited.

Signed-off-by: Liu Chuansheng &lt;chuansheng.liu@intel.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: core: Simplify and fix for SD switch processing</title>
<updated>2012-07-22T19:25:47Z</updated>
<author>
<name>Aaron Lu</name>
<email>aaron.lu@amd.com</email>
</author>
<published>2012-07-03T06:16:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a39ca6ae0a08994a59d017a445939e164bc77fd5'/>
<id>urn:sha1:a39ca6ae0a08994a59d017a445939e164bc77fd5</id>
<content type='text'>
In mmc_read_switch, just do a one time mode 0 switch command to get the
support bits information, no need to do multiple times as the support
bits do not change with different arguments.

And no need to check current limit support bits, as these bits are
fixed according to the signal voltage. If the signal voltage is 1.8V,
the support bits would be 0xf and if the signal voltage is 3.3V, the
support bits would be 0x01. We will check host's ability to set the
current limit.

Signed-off-by: Aaron Lu &lt;aaron.lu@amd.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: core: correct invalid error checking</title>
<updated>2012-07-21T04:02:24Z</updated>
<author>
<name>Alan Cox</name>
<email>alan@linux.intel.com</email>
</author>
<published>2012-07-02T17:55:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b63b5e819d5b21ae493c17c356018ffa98d3ee1c'/>
<id>urn:sha1:b63b5e819d5b21ae493c17c356018ffa98d3ee1c</id>
<content type='text'>
The effect of the existing code is that we continue blindly when we
should warn about an invalid allocation unit.

Reported-by: dcb314@hotmail.com
Resolves-bug: https://bugzilla.kernel.org/show_bug.cgi?id=44061
Signed-off-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdhci: only set 200mA support for 1.8v if 200mA is available</title>
<updated>2012-07-21T04:02:23Z</updated>
<author>
<name>Philip Rakity</name>
<email>prakity@marvell.com</email>
</author>
<published>2012-05-28T01:36:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0aa6770000bafa65c17cf44b6619d328d4fc79b3'/>
<id>urn:sha1:0aa6770000bafa65c17cf44b6619d328d4fc79b3</id>
<content type='text'>
max_current_caps can return 0 if not available from the sd controller.
If no regulator is present or the regulator specifies a current
less then 200ma, we no longer still set the 200mA caps bit anyway.

Signed-off-by: Philip Rakity &lt;prakity@marvell.com&gt;
Reviewed-by: Aaron Lu &lt;aaron_lu@amd.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: prohibit card detection when host is not ready</title>
<updated>2012-07-21T04:02:21Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2012-06-14T08:17:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d9adcc12860d76cf3401c6ab7c0406b15b356b7a'/>
<id>urn:sha1:d9adcc12860d76cf3401c6ab7c0406b15b356b7a</id>
<content type='text'>
Currently mmc host drivers have to decide whether to enable card
detection before calling mmc_add_host() -- in which case a card
insertion event can arrive before the host has been completely
initialised -- or after mmc_add_host(), in which case the initial
card detection can be problematic.

This patch adds an explicit indication of when card detection should
not be carried out. With it in place enabling card detection before
calling mmc_add_host() should be safe. Similarly, disabling it again
after calling mmc_remove_host() will avoid any races.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: core: add WP pin handler to slot functions</title>
<updated>2012-07-21T04:02:18Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2012-05-01T14:59:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5aa7dad305594ea30d21e23b3036565042adf50c'/>
<id>urn:sha1:5aa7dad305594ea30d21e23b3036565042adf50c</id>
<content type='text'>
Card Write-Protect pin is often implemented, using a GPIO, which makes
it simple to provide a generic handler for it.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: core: convert slot functions to managed allocation</title>
<updated>2012-07-21T04:02:17Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2012-05-01T14:51:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a7d1a1ebd8f5858a812ac3d5fbbc178b4959a63b'/>
<id>urn:sha1:a7d1a1ebd8f5858a812ac3d5fbbc178b4959a63b</id>
<content type='text'>
This prepares for the addition of further slot functions.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
</feed>
