[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c3c97ce1-4aaa-4e85-d2c3-275f5247c0cc@marvell.com>
Date: Thu, 23 Mar 2017 13:32:23 +0800
From: Ziji Hu <huziji@...vell.com>
To: Ulf Hansson <ulf.hansson@...aro.org>,
Gregory CLEMENT <gregory.clement@...e-electrons.com>
CC: Adrian Hunter <adrian.hunter@...el.com>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
Jason Cooper <jason@...edaemon.net>,
Andrew Lunn <andrew@...n.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Mike Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>,
linux-clk <linux-clk@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Jimmy Xu <zmxu@...vell.com>,
Jisheng Zhang <jszhang@...vell.com>,
Nadav Haklai <nadavh@...vell.com>, Ryan Gao <ygao@...vell.com>,
Doug Jones <dougj@...vell.com>, Victor Gu <xigu@...vell.com>,
"Wei(SOCP) Liu" <liuw@...vell.com>,
Wilson Ding <dingwei@...vell.com>,
Yehuda Yitschak <yehuday@...vell.com>,
Marcin Wojtas <mw@...ihalf.com>,
Hanna Hawa <hannah@...vell.com>,
Kostya Porotchkin <kostap@...vell.com>
Subject: Re: [EXT] Re: [PATCH v6 07/14] dt: bindings: Add bindings for Marvell
Xenon SD Host Controller
Hi Ulf,
On 2017/3/15 20:48, Ulf Hansson wrote:
> [...]
>
>> +
>> +Example:
>> +- For eMMC:
>> +
>> + sdhci@...000 {
>> + compatible = "marvell,armada-ap806-sdhci";
>> + reg = <0xaa0000 0x1000>;
>> + interrupts = <GIC_SPI 13 IRQ_TYPE_LEVEL_HIGH>
>> + clocks = <&emmc_clk>;
>> + clock-names = "core";
>> + bus-width = <4>;
>> + marvell,xenon-phy-slow-mode;
>> + marvell,xenon-tun-count = <11>;
>
> There's no vmmc-supply here.
>
> How do you control power to the eMMC card?
>
Sorry for the delayed reply.
Just confirmed with the engineers.
It seems that there is a regulator.
I will ask for a complete node example.
>> +
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + apm_mmccard: mmccard@0 {
>> + compatible = "mmc-card";
>> + reg = <0>;
>> + };
>> + };
>> +
>> +- For SD/SDIO:
>> +
>> + sdhci@...000 {
>> + compatible = "marvell,armada-cp110-sdhci";
>> + reg = <0xab0000 0x1000>;
>> + interrupts = <GIC_SPI 55 IRQ_TYPE_LEVEL_HIGH>
>> + vqmmc-supply = <&sd_regulator>;
>
> I guess you know vqmmc is for the I/O voltage.
>
> Again, how do you power the SD/SDIO card? No vmmc?
The vmmc-supply regulator does exist according to the engineer.
I will ask them to provide a complete one.
>
>> + clocks = <&sdclk>;
>> + clock-names = "core";
>> + bus-width = <4>;
>> + marvell,xenon-tun-count = <9>;
>> + };
>> +
>> +- For eMMC with compatible "marvell,armada-3700-sdhci":
>> +
>> + sdhci@...000 {
>> + compatible = "marvell,armada-3700-sdhci";
>> + reg = <0xaa0000 0x1000>,
>> + <phy_addr 0x4>;
>> + interrupts = <GIC_SPI 13 IRQ_TYPE_LEVEL_HIGH>
>> + clocks = <&emmcclk>;
>> + clock-names = "core";
>> + bus-width = <8>;
>> + mmc-ddr-1_8v;
>> + mmc-hs400-1_8v;
>
> Again, no vmmc?
>
The engineer told me the power to eMMC card is fixed on this platform.
They don't implement a specific regulator for eMMC core power.
>> +
>> + marvell,pad-type = "fixed-1-8v";
>> +
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + mmccard: mmccard@0 {
>> + compatible = "mmc-card";
>> + reg = <0>;
>> + };
>> + };
>> +
>> +- For SD/SDIO with compatible "marvell,armada-3700-sdhci":
>> +
>> + sdhci@...000 {
>> + compatible = "marvell,armada-3700-sdhci";
>> + reg = <0xab0000 0x1000>,
>> + <phy_addr 0x4>;
>> + interrupts = <GIC_SPI 55 IRQ_TYPE_LEVEL_HIGH>
>> + vqmmc-supply = <&sd_regulator>;
>
> Again, no vmmc?
>
It seems that the core power to SD is also fixed.
>> + clocks = <&sdclk>;
>> + clock-names = "core";
>> + bus-width = <4>;
>> +
>> + marvell,pad-type = "sd";
>> + };
>> --
>> git-series 0.9.1
>
>
> Kind regards
> Uffe
>
Powered by blists - more mailing lists