Hi,
On Thu, 17 Apr 2014 06:33:59 -0700
Antoine Ténart wrote:
> Sebastian,
>
> On Wed, Apr 16, 2014 at 04:26:06PM +0200, Sebastian Hesselbarth wrote:
> > On 04/16/2014 02:40 PM, Antoine Ténart wrote:
> > >Add a Driver to support the SDHCI controller of the Marvell Berlin SoCs.
> > >This controll
This series updates SDHCI to use the common regulator infrastructure that mmc
core provides.
Tim Kryger (2):
mmc: sdhci: Use supplies in common mmc_host struct
mmc: sdhci: Use common mmc_regulator_get_supply
drivers/mmc/host/sdhci.c | 96 +
incl
Replace some buggy code with a call to mmc_regulator_get_supply.
When external regulator provides VDD, ocr_avail is set directly based on
the supported voltage range. This allows for the use of regulators that
can't provide exactly 1.8v, 3.0v, or 3.3v. Commit cec2e21 had attempted
to address thi
Switch the common SDHCI code over to use mmc_host's regulator pointers
and remove the ones in the sdhci_host structure.
Signed-off-by: Tim Kryger
---
drivers/mmc/host/sdhci.c | 71 -
include/linux/mmc/sdhci.h |3 --
2 files changed, 38 insertion
It is important that callers of mmc_regulator_get_supply know if either
vmmc or vqmmc are present but not yet available. To support this need,
modify this function to return zero except when either of the regulator
get operations fail with -EPROBE_DEFER. Current callers don't check the
return val
Sebastian,
On Wed, Apr 16, 2014 at 04:26:06PM +0200, Sebastian Hesselbarth wrote:
> On 04/16/2014 02:40 PM, Antoine Ténart wrote:
> >Add a Driver to support the SDHCI controller of the Marvell Berlin SoCs.
> >This controller supports 3 sockets.
>
> nit: Isn't it three controller with one socket e
We got a P2041 Freescale CPU with a built in MMC controller(eSDHC)
conforming to MMC version 4.2 but
we would like use the some features from a 4.5 eMMC memory(reliable write,
discard etc.).
What 4.5 features, if any, can I use in a 4.2 eMMC controller?
Jocke
--
To unsubscribe from this list:
