From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 1/2] ARM64: dts: meson-gxbb: add MMC support
Date: Thu, 04 Aug 2016 15:58:55 -0700 [thread overview]
Message-ID: <m2oa58nntc.fsf@baylibre.com> (raw)
In-Reply-To: <20160804181556.GA13000@rob-hp-laptop> (Rob Herring's message of "Thu, 4 Aug 2016 13:15:56 -0500")
Hi Rob,
Rob Herring <robh@kernel.org> writes:
> On Wed, Aug 03, 2016 at 04:18:42PM -0700, Kevin Hilman wrote:
>> Add binding and basic support for the SD/eMMC controller on Amlogic
>> S905/GXBB devices.
>>
>> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
[...]
>> + mmc_iv: gpio-regulator {
>> + compatible = "regulator-gpio";
>> +
>> + regulator-name = "mmc-gpio-supply";
>> + regulator-min-microvolt = <1800000>;
>> + regulator-max-microvolt = <3300000>;
>> +
>> + gpios = <&gpio_ao GPIOAO_3 GPIO_ACTIVE_HIGH>;
>> + gpio-states = <0 1>;
>> +
>> + /*
>> + * Based on ODROID-C2 schematics:
>> + * signal name: IO_TF_3V3N_1V8, GPIOAO bit 3
>> + */
>> + states = <3300000 0
>> + 1800000 1>;
>
> There are multiple things wrong in this node based on the regulator-gpio
> documentation.
I see I got the property name wrong, and the number of elements wrong,
and this fixes those issues:
- gpio-states = <0 1>;
+ gpios-states = <0>;
By "multiple", did you mean more than those 2? If so, I'm not seeing
what else is wrong.
[...]
>> + mmc_iv: gpio-regulator {
>> + compatible = "regulator-gpio";
>> +
>> + regulator-name = "mmc-gpio-supply";
>> + regulator-min-microvolt = <1800000>;
>> + regulator-max-microvolt = <3300000>;
>> +
>> + gpios = <&gpio_ao GPIOAO_5 GPIO_ACTIVE_HIGH>;
>> + gpio-states = <0 1>;
>> +
>> + /* Based on P200 schematics, signal CARD_1.8V/3.3V_CTR */
>> + states = <1800000 0
>> + 3300000 1>;
>> + };
>> +
>> + vddio_boot: regulator {
> [...]
>> + vcc_3v3: regulator {
>
> This won't even compile as you have the same node name twice.
Oops, it's wrong indeed, but in fact, it does compile, otherwise I
would've caught that.. Even if I remove the labels, it still compiles.
Interesting.
Anyways, I'll make those unique node-names in the next spin.
Thanks for the review,
Kevin
next prev parent reply other threads:[~2016-08-04 22:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 23:18 [PATCH v2 1/2] ARM64: dts: meson-gxbb: add MMC support Kevin Hilman
2016-08-03 23:18 ` [PATCH v2 2/2] MMC: meson: initial support for GXBB platforms Kevin Hilman
2016-08-23 1:21 ` Stephen Boyd
2016-09-07 23:02 ` Kevin Hilman
2016-09-08 1:18 ` Stephen Boyd
2016-08-24 11:53 ` Ulf Hansson
2016-09-13 15:53 ` Kevin Hilman
2016-08-04 18:15 ` [PATCH v2 1/2] ARM64: dts: meson-gxbb: add MMC support Rob Herring
2016-08-04 22:58 ` Kevin Hilman [this message]
2016-08-05 2:45 ` Rob Herring
[not found] ` <20160805034623.GA1883@excalibur.cnev.de>
2016-08-05 15:22 ` Kevin Hilman
2016-08-14 5:25 ` kbuild test robot
2016-08-15 21:33 ` Kevin Hilman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2oa58nntc.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).