On 04/17/2014 05:33 AM, Jisheng Zhang wrote:
> On Wed, 16 Apr 2014 05:40:10 -0700
> Antoine Ténart wrote:
>> Add the SDHCI nodes for the Marvell Berlin BG2Q, using the berlin-sdhci
>> driver.
[...]
>> +sdhci0: sdhci@ab {
>> +compatible = "marvell,berlin2q-sdhci"
Hi Antoine,
On Wed, 16 Apr 2014 05:40:10 -0700
Antoine Ténart wrote:
> Add the SDHCI nodes for the Marvell Berlin BG2Q, using the berlin-sdhci
> driver.
>
> Signed-off-by: Antoine Ténart
> ---
> arch/arm/boot/dts/berlin2q.dtsi | 40
> 1 file changed, 40
On 04/16/2014 05:08 PM, Andrew Bresticker wrote:
> VDDIO_SDMMC3 is the VQMMC (I/O) supply, not the VMMC (core) supply,
> for the SD slot on Venice2.
I've applied this (one patch) to Tegra's for-3.16/dt branch.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a
Program TEGRA_SDHCI_VENDOR_MISC_CTRL so that UHS modes aren't advertised
in SDHCI_CAPABILITIES_1. While the Tegra SDHCI controller does support
these modes, they require Tegra-specific tuning and calibration routines
which the driver does not support yet.
Signed-off-by: Andrew Bresticker
---
No
The following patches fix a couple of issues which prevented Venice2
boards from booting via eMMC and SD card reliably. Note that this
includes disabling UHS support since SDR50 and above require a
Tegra-specific tuning procedure which is not supported yet (and still
seems to have issues even in d
Tegra SDHCI controllers, by default, report a base clock frequency
of 208Mhz in SDHCI_CAPABILTIES which may or may not be equal to the
actual base clock frequency. This is because the clock rate is
configured by the clock controller, which is external to the SD/MMC
controller. Since the SD/MMC co
VDDIO_SDMMC3 is the VQMMC (I/O) supply, not the VMMC (core) supply,
for the SD slot on Venice2.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- removed vqmmc supply for eMMC
---
arch/arm/boot/dts/tegra124-venice2.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ar
On Wed, Apr 16, 2014 at 01:15:53PM -0700, Andrew Bresticker wrote:
> Not true. If !CONFIG_REGULATOR, regulator_get() and co. will return
> NULL. Normally it is ok to ignore this case, but the sdhci driver
> will call regulator_is_supported_voltage() on vqmmc to determine
> whether 1.8V signallin
On Wed, Apr 16, 2014 at 9:19 AM, Stephen Warren wrote:
> On 04/15/2014 06:29 PM, Andrew Bresticker wrote:
>>> sdhci@0,700b0600 {
>>> status = "okay";
>>> bus-width = <8>;
>>> + vqmmc-supply = <&vddio_1v8>;
>>
>> It turns out this bit isn't need
Hi Mike,
On Mon, Apr 7, 2014 at 6:11 AM, Mike Looijmans wrote:
> On 04/07/2014 02:51 PM, Arnd Bergmann wrote:
>>
>> On Monday 07 April 2014 14:32:20 Mike Looijmans wrote:
>>>
>>> On 04/07/2014 02:25 PM, Arnd Bergmann wrote:
>>>
>>> Judging from the kernel output, regulator_get_optional returns -E
The existing PXA MMC driver cannot get DMA channels in a proper
way from the respective device tree binding.
This patch provides temporary workaround which allows using the
existing driver in DT machines by pointing to the proper
dmaengine-based "marvell,pdma-1.0" DMA.
Even though the new DMA pro
On 04/15/2014 06:29 PM, Andrew Bresticker wrote:
>> sdhci@0,700b0600 {
>> status = "okay";
>> bus-width = <8>;
>> + vqmmc-supply = <&vddio_1v8>;
>
> It turns out this bit isn't needed as the initialization failures are
> instead due to +3V3_RUN
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 each?
Signed-off-by: Antoine Ténart
---
drivers/mmc/host/Kconfig| 11
dri
Hi Andrew,
On Wed, Apr 16, 2014 at 03:09:15PM +0200, Andrew Lunn wrote:
> On Wed, Apr 16, 2014 at 02:40:10PM +0200, Antoine Ténart wrote:
> > Add the SDHCI nodes for the Marvell Berlin BG2Q, using the berlin-sdhci
> > driver.
> >
> > Signed-off-by: Antoine Ténart
> > ---
> > arch/arm/boot/dts/b
On Wed, Apr 16, 2014 at 02:40:10PM +0200, Antoine Ténart wrote:
> Add the SDHCI nodes for the Marvell Berlin BG2Q, using the berlin-sdhci
> driver.
>
> Signed-off-by: Antoine Ténart
> ---
> arch/arm/boot/dts/berlin2q.dtsi | 40
> 1 file changed, 40 insert
Joe,
On Wed, Apr 16, 2014 at 05:56:34AM -0700, Joe Perches wrote:
> On Wed, 2014-04-16 at 14:40 +0200, Antoine Ténart wrote:
> > Add a Driver to support the SDHCI controller of the Marvell Berlin SoCs.
> > This controller supports 3 sockets.
>
> trivial notes:
>
> > diff --git a/drivers/mmc/host
On Wed, 2014-04-16 at 14:40 +0200, Antoine Ténart wrote:
> Add a Driver to support the SDHCI controller of the Marvell Berlin SoCs.
> This controller supports 3 sockets.
trivial notes:
> diff --git a/drivers/mmc/host/sdhci-berlin.c b/drivers/mmc/host/sdhci-berlin.c
[]
> +static struct sdhci_ops s
Enable the SD Card reader and the internal eMMC on the Berlin BG2Q DMP
using two of the SDHCI nodes of the Berlin BG2Q.
Signed-off-by: Antoine Ténart
---
arch/arm/boot/dts/berlin2q-marvell-dmp.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/berlin2q-marvell-dmp.
Add a Driver to support the SDHCI controller of the Marvell Berlin SoCs.
This controller supports 3 sockets.
Signed-off-by: Antoine Ténart
---
drivers/mmc/host/Kconfig| 11
drivers/mmc/host/Makefile | 1 +
drivers/mmc/host/sdhci-berlin.c | 129 ++
Add the binding documentation for the Marvell Berlin SDHCI driver.
Signed-off-by: Antoine Ténart
---
Documentation/devicetree/bindings/mmc/sdhci-berlin.txt | 18 ++
1 file changed, 18 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-berlin.txt
diff -
Add the SDHCI nodes for the Marvell Berlin BG2Q, using the berlin-sdhci
driver.
Signed-off-by: Antoine Ténart
---
arch/arm/boot/dts/berlin2q.dtsi | 40
1 file changed, 40 insertions(+)
diff --git a/arch/arm/boot/dts/berlin2q.dtsi b/arch/arm/boot/dts/berl
This series adds the support for the SDHCI controller for Marvell Berlin
SoCs and enable the SD card reader and eMMC for the BG2Q DMP. The
controller supports 3 sockets.
Tested on the BG2Q DMP.
This series applies on top of Alexandre's patches for the Berlin's pll:
https://patchwork.kernel.org/pa
On Fri, 11 Apr 2014, rogera...@realtek.com wrote:
> From: Roger Tseng
>
> Explain why there is no need to have a symmetric LED turn-on in resume handler
> while calling rtsx_usb_turn_off_led() in suspend handler.
>
> Signed-off-by: Roger Tseng
> ---
> drivers/mfd/rtsx_usb.c | 6 ++
> 1 fi
> From: Roger Tseng
>
> Fix two possible race condition generated by misuse of del_timer in
> rtsx_usb_bulk_transfer_sglist() and uninitialized timers before
> mfd_add_devices
> in rtsx_usb_probe().
>
> Signed-off-by: Roger Tseng
> ---
> drivers/mfd/rtsx_usb.c | 8
> 1 file changed,
Hi Andrew,
> From: Roger Tseng
>
> Realtek USB memstick host driver provides memstick host support based on the
> Realtek USB card reader MFD driver.
>
> Signed-off-by: Roger Tseng
> ---
> drivers/memstick/host/Kconfig | 10 +
> drivers/memstick/host/Makefile | 1 +
> drivers/me
> From: Roger Tseng
>
> This patchset adds modules to support Realtek USB vendor specific class
> flash
> card reader: one base module in MFD subsystem and two host modules in
> both mmc
> and memstick subsystems. The architecture is similar to rtsx_pci.
>
> >>>
On 15 April 2014 10:33, Linus Walleij wrote:
> The next step in modernization of GPIO is to let drivers handle
> descriptors rather than integer numbers representing GPIO pins,
> akin to how clocks or regulators are already handled today.
>
> This patch makes the MMCI driver use GPIO descriptos in
On 16 April 2014 05:19, Roger wrote:
> On 04/11/2014 06:36 PM, Oliver Neukum wrote:
>>
>> On Fri, 2014-04-11 at 11:28 +0100, Lee Jones wrote:
>
> From: Roger Tseng
>
> This patchset adds modules to support Realtek USB vendor specific class
> flash
> card reader: one base m
On 15 April 2014 19:09, Tim Kryger wrote:
> On Fri, Apr 11, 2014 at 1:15 AM, Ulf Hansson wrote:
>
>> I have seen some patches around lately touching the code for handling
>> the regulators (vcc and vccq) in sdhci.
>
> Was it this patch you were thinking of or something else?
>
> http://www.spinic
Hello all,
in attachment is current version of driver for Alcor Micro AU6601 which
is based on my RE work. In current state it works with most cards i have
except of "MMC mobile 1GB Kingstone", this card fail to start if
controller set to 4bit mode. All other cards work with 4bit mode without
visi
30 matches
Mail list logo
