<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/include/linux/mmc/sdhci.h, branch linux-3.11.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-3.11.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-3.11.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2013-07-05T16:48:35Z</updated>
<entry>
<title>mmc: esdhc: Fix bug when writing to SDHCI_HOST_CONTROL register</title>
<updated>2013-07-05T16:48:35Z</updated>
<author>
<name>Oded Gabbay</name>
<email>ogabbay@advaoptical.com</email>
</author>
<published>2013-07-05T16:48:35Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=dcaff04d36fd7f22973bf4fc108912ce19bcef4f'/>
<id>urn:sha1:dcaff04d36fd7f22973bf4fc108912ce19bcef4f</id>
<content type='text'>
The P2020 has a non-standard implementation of the SDHCI_HOST_CONTROL
register. This patch adds a QUIRK in the SDHCI header to signal that
a host controller has a non-standard SDHCI_HOST_CONTROL register. The
patch adds a check to the function esdhc_writeb in file
sdhci-of-esdhc.c, where it checks if the write is done to the
SDHCI_HOST_CONTROL register and th host has the above mentioned QUIRK,
then the function simply returns instead of writing to the register.
The patch also detects if the processor is P2020 (by looking in dev
tree) and if so, adds the QUIRK to the host-&gt;quirk2

Signed-off-by: Oded Gabbay &lt;ogabbay@advaoptical.com&gt;
Reviewed-by: Anton Vorontsov &lt;anton@enomsg.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdhci: fix caps2 for HS200</title>
<updated>2013-06-27T16:39:24Z</updated>
<author>
<name>Giuseppe CAVALLARO</name>
<email>peppe.cavallaro@st.com</email>
</author>
<published>2013-06-12T06:16:38Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=156e14b126ffb6f040bc6f1aff3c51077e42a744'/>
<id>urn:sha1:156e14b126ffb6f040bc6f1aff3c51077e42a744</id>
<content type='text'>
Although the HC supports HS200 (eMMC) the caps2 are always zero; this
means there's no way to use the super speed mode (when init the card).

If the HC support SDR104, for SD3.0, so it also supports HS200 for eMMC
and this patch just sets the MMC_CAP2_HS200 in the host caps2 field.

Reported-by: Youssef Triki &lt;youssef.triki@st.com&gt;
Signed-off-by: Giuseppe Cavallaro &lt;peppe.cavallaro@st.com&gt;
Reviewed-by: Philip Rakity &lt;prakity@nvidia.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdhci: add ability to stay runtime-resumed if the card is powered up</title>
<updated>2013-05-26T18:23:23Z</updated>
<author>
<name>Adrian Hunter</name>
<email>adrian.hunter@intel.com</email>
</author>
<published>2013-05-06T09:17:32Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=f0710a557cb17746b09234f01073a2cdafe4f4a5'/>
<id>urn:sha1:f0710a557cb17746b09234f01073a2cdafe4f4a5</id>
<content type='text'>
If card power is dependent on SD bus power then the host controller
must not be runtime suspended while the card is powered up.  Add
the ability to stay runtime-resumed in that case and enable it with a new
quirk SDHCI_QUIRK2_CARD_ON_NEEDS_BUS_ON.

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: enhance preset value function</title>
<updated>2013-02-24T19:37:11Z</updated>
<author>
<name>Kevin Liu</name>
<email>kliu5@marvell.com</email>
</author>
<published>2013-01-31T03:31:37Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=52983382c74f59a3953e622d7661a24e1bc4388a'/>
<id>urn:sha1:52983382c74f59a3953e622d7661a24e1bc4388a</id>
<content type='text'>
4d55c5a1 ("mmc: sdhci: enable preset value after uhs initialization")
added preset value support and enabled it by default during sd card init.

Below are the enhancements introduced by this patch:

1. In current code, preset value is enabled after setting clock finished,
which means the clock is manually set by driver firstly and then suddenly
switched to preset value at this point. So the first setting is useless
and unnecessary. What's more, the first clock setting may differ from the
preset one.  The better way is enable preset value just after switch to
UHS mode so the preset value can take effect immediately. So move preset
value enable from mmc_sd_init_card to sdhci_set_ios which will be called
during set timing.

2. In current code, preset value is disabled at the beginning of
mmc_attach_sd.  It's too late since low freq (400khz) should be set in
mmc_power_up.  So move preset value disable to sdhci_set_ios which will
be called during power up.

3. host-&gt;clock and ios-&gt;drv_type should also be updated according to the
preset value if it's enabled. Current code missed this.

4. This patch also introduce a quirk to disable preset value in case
preset value doesn't work.

This patch has been verified on sdhci-pxav3 platform with both preset
enabled and disabled.

Signed-off-by: Kevin Liu &lt;kliu5@marvell.com&gt;
Reviewed-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdhci: add quirk for lack of 1.8v support</title>
<updated>2012-12-06T18:55:04Z</updated>
<author>
<name>Daniel Drake</name>
<email>dsd@laptop.org</email>
</author>
<published>2012-11-25T18:01:19Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=6a66180a252f5856fc25de69c6313831f343f50f'/>
<id>urn:sha1:6a66180a252f5856fc25de69c6313831f343f50f</id>
<content type='text'>
The OLPC XO-1.75 laptop includes a SDHCI controller which is 1.8v
capable, and it truthfully reports so in its capabilities. This
alternate voltage is used for driving new "UHS-I" SD cards at their
full speed.

However, what the controller doesn't know is that the motherboard
physically doesn't have a 1.8v supply available.

Add a quirk so that systems such as this one can override disable
1.8v support, adding support for UHS-I cards (by running them at
3.3v).

This avoids a problem where the system would first try to run the
card at 1.8v, fail, and then not be able to fully reset the card
to retry at the normal 3.3v voltage.

This is more appropriate than using the MISSING_CAPS quirk, which
is intended for cases where the SDHCI controller is actually lying
about its capabilities, and would force us to somehow override both
caps words from another source.

Signed-off-by: Daniel Drake &lt;dsd@laptop.org&gt;
Reviewed-by: Philip Rakity &lt;prakity@nvidia.com&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://universe.0xinfinity.dev/distro/kernel/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>
<entry>
<title>mmc: sdhci-of-esdhc: disable CMD23 for some Freescale SoCs</title>
<updated>2012-11-07T19:55:29Z</updated>
<author>
<name>Jerry Huang</name>
<email>Chang-Ming.Huang@freescale.com</email>
</author>
<published>2012-10-25T05:47:19Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=63ef5d8c28b2a944f104d854254941e7375c85a3'/>
<id>urn:sha1:63ef5d8c28b2a944f104d854254941e7375c85a3</id>
<content type='text'>
CMD23 causes lots of errors in kernel on some freescale SoCs
(P1020, P1021, P1022, P1024, P1025 and P4080) when MMC card used,
which is because these controllers does not support CMD23,
even on the SoCs which declares CMD23 is supported.
Therefore, we'll not use CMD23.

Signed-off-by: Jerry Huang &lt;Chang-Ming.Huang@freescale.com&gt;
Signed-off-by: Shaohui Xie &lt;Shaohui.Xie@freescale.com&gt;
Acked-by: Anton Vorontsov &lt;cbouatmailru@gmail.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdhci: Add regulator support for vccq (voltage regualor)</title>
<updated>2012-09-04T17:58:13Z</updated>
<author>
<name>Philip Rakity</name>
<email>prakity@marvell.com</email>
</author>
<published>2012-07-23T22:56:23Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=6231f3de1332b2a8a90e0c598ab6acc8f1eff7c1'/>
<id>urn:sha1:6231f3de1332b2a8a90e0c598ab6acc8f1eff7c1</id>
<content type='text'>
On some systems the host controller does not support vccq
signaling.  This is supplied by a dedicated regulator (vqmmc).
Add support for this regulator.

Signed-off-by: Philip Rakity &lt;prakity@marvell.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: sdhci: Introduce new flag SDHCI_USING_RETUNING_TIMER</title>
<updated>2012-07-22T19:25:49Z</updated>
<author>
<name>Aaron Lu</name>
<email>aaron.lu@amd.com</email>
</author>
<published>2012-07-04T05:29:09Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=973905feab85416784f36cc94b868392fd465ef4'/>
<id>urn:sha1:973905feab85416784f36cc94b868392fd465ef4</id>
<content type='text'>
Add a new flag of SDHCI_USING_RETUNING_TIMER to represent if the host
is using a retuning timer for the card inserted.

This flag is set when the host does tuning the first time for the card
and the host's retuning mode is 1. This flag is used afterwards whenever
needs to decide if the host is currently using a retuning timer.

This flag is cleared when the card is removed in sdhci_reinit.

The set/clear of the flag and the start/stop of the retuning timer is
associated with the card's init/remove time, so there is no need to
touch it when the host is to be removed as at that time the card should
have already been removed.

Signed-off-by: Aaron Lu &lt;aaron.lu@amd.com&gt;
Reviewed-by: Girish K S &lt;girish.shivananjappa@linaro.org&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: sdhci: Allow caps[1] to be set via SDHCI_QUIRK_MISSING_CAPS</title>
<updated>2012-07-22T19:25:44Z</updated>
<author>
<name>Philip Rakity</name>
<email>prakity@marvell.com</email>
</author>
<published>2012-06-28T04:49:27Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=bd6a8c30faf19b4e7abace93fb89efd6d72607ec'/>
<id>urn:sha1:bd6a8c30faf19b4e7abace93fb89efd6d72607ec</id>
<content type='text'>
Currently only the capability_0 register can be set if
SDHCI_QUIRK_MISSING_CAPS is defined.  This is a problem when
the capability_1 register also needs changing.  Use the quirk
SDHCI_QUIRK_MISSING_CAPS to allow both registers to be set.

Redefining caps[1] is useful when the board design does not
support 1.8v vccq so UHS modes are not available.  The code that
calls sdhci_add_host can then detect this condition and adjust
the caps so the UHS mode will not be attempted on UHS cards.

Signed-off-by: Philip Rakity &lt;prakity@marvell.com&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
</feed>
