public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Soeren Moch <smoch@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] arm: dts: rk3399-rockpro64: sync dts from linux kernel
Date: Fri, 8 Nov 2019 09:45:52 +0100	[thread overview]
Message-ID: <2140942e-2db8-87ef-b64d-75297a04be4b@web.de> (raw)
In-Reply-To: <c817a7b3-840c-3ee5-5eed-f79a17f9e841@rock-chips.com>



On 08.11.19 04:22, Kever Yang wrote:
>
> On 2019/11/7 下午7:11, Soeren Moch wrote:
>> The most important change for u-boot is the fix for the vdd-log pwm
>> voltage regulator to avoid overvoltage for the VD_LOGIC power domain.
>>
>> Signed-off-by: Soeren Moch <smoch@web.de>
>> =2D--
>> Cc: Kever Yang <kever.yang@rock-chips.com>
>> Cc: u-boot at lists.denx.de
>> =2D--
>
> Why  is the "=2D- -" here?
'git send-email' encodes the patch this way. I use git version 2.17.1 .
Apparently this this done to avoid problems with MTAs, I also saw 'From'
in a patch description encoded in this special way.
Seems to be no problem for other tools, e.g. u-boot patchwork converts
this back to the more traditional readable form.

I'm not sure what I should do about this, seems to be more a feature
than a bug.
>
> Otherwise looks good to me.
>
>
> Reviewed-by: Kever Yang<kever.yang@rock-chips.com>
Thanks,
Soeren
>
> Thanks,
> - Kever
>
>>   arch/arm/dts/rk3399-rockpro64.dts | 57 ++++++++++++++++++++++++++-----
>>   1 file changed, 49 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/arm/dts/rk3399-rockpro64.dts
>> b/arch/arm/dts/rk3399-rockp=
>> ro64.dts
>> index 1f2394e058..e544deb61d 100644
>> =2D-- a/arch/arm/dts/rk3399-rockpro64.dts
>> +++ b/arch/arm/dts/rk3399-rockpro64.dts
>> @@ -58,6 +58,13 @@
>>           };
>>       };
>>
>> +    fan: pwm-fan {
>> +        compatible =3D "pwm-fan";
>> +        #cooling-cells =3D <2>;
>> +        fan-supply =3D <&vcc12v_dcin>;
>> +        pwms =3D <&pwm1 0 50000 0>;
>> +    };
>> +
>>       sdio_pwrseq: sdio-pwrseq {
>>           compatible =3D "mmc-pwrseq-simple";
>>           clocks =3D <&rk808 1>;
>> @@ -166,7 +173,7 @@
>>           regulator-always-on;
>>           regulator-boot-on;
>>           regulator-min-microvolt =3D <800000>;
>> -        regulator-max-microvolt =3D <1400000>;
>> +        regulator-max-microvolt =3D <1700000>;
>>           vin-supply =3D <&vcc5v0_sys>;
>>       };
>>   };
>> @@ -222,6 +229,10 @@
>>       status =3D "okay";
>>   };
>>
>> +&hdmi_sound {
>> +    status =3D "okay";
>> +};
>> +
>>   &gpu {
>>       mali-supply =3D <&vdd_gpu>;
>>       status =3D "okay";
>> @@ -236,8 +247,8 @@
>>       rk808: pmic at 1b {
>>           compatible =3D "rockchip,rk808";
>>           reg =3D <0x1b>;
>> -        interrupt-parent =3D <&gpio1>;
>> -        interrupts =3D <21 IRQ_TYPE_LEVEL_LOW>;
>> +        interrupt-parent =3D <&gpio3>;
>> +        interrupts =3D <10 IRQ_TYPE_LEVEL_LOW>;
>>           #clock-cells =3D <1>;
>>           clock-output-names =3D "xin32k", "rk808-clkout2";
>>           pinctrl-names =3D "default";
>> @@ -504,11 +515,25 @@
>>       status =3D "okay";
>>
>>       bt656-supply =3D <&vcc1v8_dvp>;
>> -    audio-supply =3D <&vcca1v8_codec>;
>> +    audio-supply =3D <&vcc_3v0>;
>>       sdmmc-supply =3D <&vcc_sdio>;
>>       gpio1830-supply =3D <&vcc_3v0>;
>>   };
>>
>> +&pcie0 {
>> +    ep-gpios =3D <&gpio2 RK_PD4 GPIO_ACTIVE_HIGH>;
>> +    num-lanes =3D <4>;
>> +    pinctrl-names =3D "default";
>> +    pinctrl-0 =3D <&pcie_perst>;
>> +    vpcie12v-supply =3D <&vcc12v_dcin>;
>> +    vpcie3v3-supply =3D <&vcc3v3_pcie>;
>> +    status =3D "okay";
>> +};
>> +
>> +&pcie_phy {
>> +    status =3D "okay";
>> +};
>> +
>>   &pmu_io_domains {
>>       pmu1830-supply =3D <&vcc_3v0>;
>>       status =3D "okay";
>> @@ -538,6 +563,10 @@
>>       };
>>
>>       pcie {
>> +        pcie_perst: pcie-perst {
>> +            rockchip,pins =3D <2 RK_PD4 RK_FUNC_GPIO &pcfg_pull_none>;
>> +        };
>> +
>>           pcie_pwr_en: pcie-pwr-en {
>>               rockchip,pins =3D <1 RK_PD0 RK_FUNC_GPIO &pcfg_pull_none>;
>>           };
>> @@ -545,7 +574,7 @@
>>
>>       pmic {
>>           pmic_int_l: pmic-int-l {
>> -            rockchip,pins =3D <1 RK_PC5 RK_FUNC_GPIO &pcfg_pull_up>;
>> +            rockchip,pins =3D <3 RK_PB2 RK_FUNC_GPIO &pcfg_pull_up>;
>>           };
>>
>>           vsel1_gpio: vsel1-gpio {
>> @@ -580,6 +609,10 @@
>>       status =3D "okay";
>>   };
>>
>> +&pwm1 {
>> +    status =3D "okay";
>> +};
>> +
>>   &pwm2 {
>>       status =3D "okay";
>>   };
>> @@ -591,7 +624,6 @@
>>
>>   &sdmmc {
>>       bus-width =3D <4>;
>> -    cap-mmc-highspeed;
>>       cap-sd-highspeed;
>>       cd-gpios =3D <&gpio0 7 GPIO_ACTIVE_LOW>;
>>       disable-wp;
>> @@ -603,12 +635,21 @@
>>
>>   &sdhci {
>>       bus-width =3D <8>;
>> -    mmc-hs400-1_8v;
>> -    mmc-hs400-enhanced-strobe;
>> +    mmc-hs200-1_8v;
>>       non-removable;
>>       status =3D "okay";
>>   };
>>
>> +&spi1 {
>> +    status =3D "okay";
>> +
>> +    flash at 0 {
>> +        compatible =3D "jedec,spi-nor";
>> +        reg =3D <0>;
>> +        spi-max-frequency =3D <10000000>;
>> +    };
>> +};
>> +
>>   &tcphy0 {
>>       status =3D "okay";
>>   };
>> =2D-
>> 2.17.1
>>
>>
>
>

  reply	other threads:[~2019-11-08  8:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 11:11 [U-Boot] [PATCH 1/2] arm: dts: rk3399-rockpro64: sync dts from linux kernel Soeren Moch
2019-11-07 11:11 ` [U-Boot] [PATCH 2/2] arm: dts: rk3399-rockpro64: slightly increase center voltage Soeren Moch
2019-11-08  3:23   ` Kever Yang
2019-11-18  2:55     ` [U-Boot] [PATCH 2/2] arm: dts: rk3399-rockpro64: slightly increase center voltage【请注意,邮件由u-boot-bounces@lists.denx.de代发】 Kever Yang
2019-11-07 20:04 ` [U-Boot] [PATCH 1/2] arm: dts: rk3399-rockpro64: sync dts from linux kernel Vasily Khoruzhick
2019-11-07 20:25   ` Soeren Moch
2019-11-07 20:28     ` Vasily Khoruzhick
2019-11-08  3:22 ` Kever Yang
2019-11-08  8:45   ` Soeren Moch [this message]
2019-11-08 11:41     ` Soeren Moch
2019-11-18  2:56   ` [U-Boot] [PATCH 1/2] arm: dts: rk3399-rockpro64: sync dts from linux kernel【请注意,邮件由u-boot-bounces@lists.denx.de代发】 Kever Yang

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=2140942e-2db8-87ef-b64d-75297a04be4b@web.de \
    --to=smoch@web.de \
    --cc=u-boot@lists.denx.de \
    /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