From: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
Cc: Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/2] ARM: dts: sun6i: Add pmic / regulator nodes to Mele A1000G quad dts
Date: Mon, 6 Jun 2016 09:23:36 +0200 [thread overview]
Message-ID: <0a42bc82-83f2-80ce-93d4-a85c5ce69e24@redhat.com> (raw)
In-Reply-To: <CAGb2v67Jo6MO7bp4JdV4hXrB4T60z4=ROkvAvE1i7dhAXk_UtQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi,
On 06-06-16 09:12, Chen-Yu Tsai wrote:
> On Sun, Jun 5, 2016 at 9:37 PM, Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>> Add pmic / regulator nodes to Mele A1000G quad dts.
>>
>> Signed-off-by: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>> ---
>> arch/arm/boot/dts/sun6i-a31-mele-a1000g-quad.dts | 88 +++++++++++++++++++++++-
>> 1 file changed, 87 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/boot/dts/sun6i-a31-mele-a1000g-quad.dts b/arch/arm/boot/dts/sun6i-a31-mele-a1000g-quad.dts
>> index e063dab..9782113 100644
>> --- a/arch/arm/boot/dts/sun6i-a31-mele-a1000g-quad.dts
>> +++ b/arch/arm/boot/dts/sun6i-a31-mele-a1000g-quad.dts
>> @@ -72,6 +72,10 @@
>> };
>> };
>>
>> +&cpu0 {
>> + cpu-supply = <®_dcdc3>;
>> +};
>> +
>> &ehci0 {
>> status = "okay";
>> };
>> @@ -85,6 +89,7 @@
>> pinctrl-0 = <&gmac_pins_mii_a>;
>> phy = <&phy1>;
>> phy-mode = "mii";
>> + phy-supply = <®_dldo1>;
>> status = "okay";
>>
>> phy1: ethernet-phy@1 {
>> @@ -101,13 +106,26 @@
>> &mmc0 {
>> pinctrl-names = "default";
>> pinctrl-0 = <&mmc0_pins_a>, <&mmc0_cd_pin_m9>;
>> - vmmc-supply = <®_vcc3v3>;
>> + vmmc-supply = <®_dcdc1>;
>> bus-width = <4>;
>> cd-gpios = <&pio 7 22 GPIO_ACTIVE_HIGH>; /* PH22 */
>> cd-inverted;
>> status = "okay";
>> };
>>
>> +&p2wi {
>> + status = "okay";
>> +
>> + axp22x: pmic@68 {
>> + compatible = "x-powers,axp221";
>> + reg = <0x68>;
>> + interrupt-parent = <&nmi_intc>;
>> + interrupts = <0 IRQ_TYPE_LEVEL_LOW>;
>> + };
>> +};
>> +
>> +#include "axp22x.dtsi"
>> +
>> &pio {
>> led_pins_m9: led_pins@0 {
>> allwinner,pins = "PH13";
>> @@ -131,6 +149,73 @@
>> };
>> };
>>
>> +®_aldo1 {
>> + regulator-min-microvolt = <3300000>;
>> + regulator-max-microvolt = <3300000>;
>> + regulator-name = "vcc-wifi";
>> +};
>> +
>> +®_aldo3 {
>> + regulator-always-on;
>> + regulator-min-microvolt = <2700000>;
>> + regulator-max-microvolt = <3300000>;
>> + regulator-name = "avcc";
>> +};
>> +
>> +®_dc5ldo {
>> + regulator-always-on;
>> + regulator-min-microvolt = <700000>;
>> + regulator-max-microvolt = <1320000>;
>> + regulator-name = "vdd-cpus"; /* This is an educated guess */
>> +};
>> +
>> +®_dcdc1 {
>> + regulator-always-on;
>> + regulator-min-microvolt = <3300000>;
>> + regulator-max-microvolt = <3300000>;
>> + regulator-name = "vcc-3v3";
>> +};
>> +
>> +®_dcdc2 {
>> + regulator-min-microvolt = <700000>;
>> + regulator-max-microvolt = <1320000>;
>> + regulator-name = "vdd-gpu";
>> +};
>> +
>> +®_dcdc3 {
>> + regulator-always-on;
>> + regulator-min-microvolt = <700000>;
>> + regulator-max-microvolt = <1320000>;
>> + regulator-name = "vdd-cpu";
>> +};
>> +
>> +®_dcdc4 {
>> + regulator-always-on;
>> + regulator-min-microvolt = <700000>;
>> + regulator-max-microvolt = <1320000>;
>> + regulator-name = "vdd-sys-dll";
>> +};
>> +
>> +®_dcdc5 {
>> + regulator-always-on;
>> + regulator-min-microvolt = <1500000>;
>> + regulator-max-microvolt = <1500000>;
>> + regulator-name = "vcc-dram";
>> +};
>> +
>> +®_dldo1 {
>> + regulator-min-microvolt = <3300000>;
>> + regulator-max-microvolt = <3300000>;
>> + regulator-name = "vcc-ethernet-phy";
>> +};
>> +
>> +®_dldo4 {
>> + regulator-always-on;
>
> Why not tie this to the usbphy? Same for the other patch.
Because both reg_usb1_vbus and reg_dldo4 need to be on
for the hub attached to usb1 to work, and I can list
only one usb1_vbus-supply.
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-06 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 13:37 [PATCH 1/2] ARM: dts: sun6i: Add pmic / regulator nodes to Mele A1000G quad dts Hans de Goede
[not found] ` <1465133880-22921-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-05 13:38 ` [PATCH 2/2] ARM: dts: sun6i: Add pmic / regulator nodes to Mele M9 dts Hans de Goede
2016-06-06 7:12 ` [PATCH 1/2] ARM: dts: sun6i: Add pmic / regulator nodes to Mele A1000G quad dts Chen-Yu Tsai
[not found] ` <CAGb2v67Jo6MO7bp4JdV4hXrB4T60z4=ROkvAvE1i7dhAXk_UtQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-06 7:23 ` Hans de Goede [this message]
[not found] ` <0a42bc82-83f2-80ce-93d4-a85c5ce69e24-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-06 7:33 ` Chen-Yu Tsai
2016-06-07 21:25 ` Maxime Ripard
2016-06-09 10:53 ` Hans de Goede
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=0a42bc82-83f2-80ce-93d4-a85c5ce69e24@redhat.com \
--to=hdegoede-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=wens-jdAy2FN1RRM@public.gmane.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).