From: "Heiko Stübner" <heiko@sntech.de>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
ocfox <i@ocfox.me>
Cc: ocfox <i@ocfox.me>
Subject: Re: [PATCH] arm64: dts: rockchip: add support for Rongpin king3399 board
Date: Sat, 01 Jul 2023 13:04:16 +0200 [thread overview]
Message-ID: <4811978.GXAFRqVoOG@diego> (raw)
In-Reply-To: <20230630173010.272469-1-i@ocfox.me>
Hi,
all of what Krzysztof said in his mail + the stuff below please:
Am Freitag, 30. Juni 2023, 19:27:52 CEST schrieb ocfox:
> king3399 is a bord from Rongpin, you can find detail about
> it here:
> (http://www.rpdzkj.com/copy_2_1703937_175104_2536441.html)
>
> This patch add basic node for the board and make it able to bring
> up.
>
> Works:
> - USB, type-C port
> - Ethernet
> - WiFi/BT
> - HDMI
> - eMMC
> - PCIe
> - sd-card
>
> Not test for other peripheral:
> - AUDIO
> - MIC
> - SIM
> - MIPI
>
> Signed-off-by: ocfox <i@ocfox.me>
I think we request a full name here and as patch author.
[...]
> + vcc3v3_sys: vcc3v3-sys {
> + compatible = "regulator-fixed";
> + regulator-name = "vcc3v3_sys";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + vin-supply = <&vcc5v0_sys>;
> + };
> +
> + // 4G Module
please use a consistent comment style ... in the "/* foobar */" style
> + vcc3v3_gsm: vcc3v3-gsm {
> + compatible = "regulator-fixed";
> + enable-active-high;
> + gpio = <&gpio4 RK_PC6 GPIO_ACTIVE_HIGH>; // bsp
> + pinctrl-names = "default";
> + pinctrl-0 = <&vcc3v3_gsm_en>;
> + regulator-name = "vcc3v3_gsm";
> + // regulator-always-on;
> + vin-supply = <&dc_12v>;
> + };
> +
> + // vdd 5v: USB 2&3, USB Hub, Type-C, HDMI, MIPI, IR
so this regulator controls all of those?
In that case maybe do it similarly to vcc1v8-s3 and use multiple labels
for the node - i.e. the line name leading to the consumer from the
schematics.
That way comparing schematics against the dts gets easier.
See
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts#n40
for an example
> + vcc5v0_host: vcc5v0-host-regulator {
> + compatible = "regulator-fixed";
> + enable-active-high;
> + regulator-boot-on;
> + gpio = <&gpio4 RK_PD6 GPIO_ACTIVE_HIGH>; // bsp
> + pinctrl-names = "default";
> + pinctrl-0 = <&vcc5v0_host_en>;
> + regulator-name = "vcc5v0_host";
> + // regulator-always-on;
> + vin-supply = <&vcc5v0_sys>;
> + };
> +
> + vcc5v0_typec0: vbus-typec-regulator {
> + compatible = "regulator-fixed";
> + enable-active-high;
> + gpio = <&gpio4 RK_PD2 GPIO_ACTIVE_HIGH>; // bsp
> + pinctrl-names = "default";
> + pinctrl-0 = <&vcc5v0_typec_en>;
> + regulator-name = "vcc5v0_typec0";
> + vin-supply = <&vcc5v0_sys>;
> + };
> +
> + vcc_sys: vcc5v0_sys: vcc5v0-sys { // bsp
> + compatible = "regulator-fixed";
> + regulator-name = "vcc5v0_sys";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + vin-supply = <&dc_12v>;
> + };
> +
> +
double empty line
Thanks
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
ocfox <i@ocfox.me>
Cc: ocfox <i@ocfox.me>
Subject: Re: [PATCH] arm64: dts: rockchip: add support for Rongpin king3399 board
Date: Sat, 01 Jul 2023 13:04:16 +0200 [thread overview]
Message-ID: <4811978.GXAFRqVoOG@diego> (raw)
In-Reply-To: <20230630173010.272469-1-i@ocfox.me>
Hi,
all of what Krzysztof said in his mail + the stuff below please:
Am Freitag, 30. Juni 2023, 19:27:52 CEST schrieb ocfox:
> king3399 is a bord from Rongpin, you can find detail about
> it here:
> (http://www.rpdzkj.com/copy_2_1703937_175104_2536441.html)
>
> This patch add basic node for the board and make it able to bring
> up.
>
> Works:
> - USB, type-C port
> - Ethernet
> - WiFi/BT
> - HDMI
> - eMMC
> - PCIe
> - sd-card
>
> Not test for other peripheral:
> - AUDIO
> - MIC
> - SIM
> - MIPI
>
> Signed-off-by: ocfox <i@ocfox.me>
I think we request a full name here and as patch author.
[...]
> + vcc3v3_sys: vcc3v3-sys {
> + compatible = "regulator-fixed";
> + regulator-name = "vcc3v3_sys";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + vin-supply = <&vcc5v0_sys>;
> + };
> +
> + // 4G Module
please use a consistent comment style ... in the "/* foobar */" style
> + vcc3v3_gsm: vcc3v3-gsm {
> + compatible = "regulator-fixed";
> + enable-active-high;
> + gpio = <&gpio4 RK_PC6 GPIO_ACTIVE_HIGH>; // bsp
> + pinctrl-names = "default";
> + pinctrl-0 = <&vcc3v3_gsm_en>;
> + regulator-name = "vcc3v3_gsm";
> + // regulator-always-on;
> + vin-supply = <&dc_12v>;
> + };
> +
> + // vdd 5v: USB 2&3, USB Hub, Type-C, HDMI, MIPI, IR
so this regulator controls all of those?
In that case maybe do it similarly to vcc1v8-s3 and use multiple labels
for the node - i.e. the line name leading to the consumer from the
schematics.
That way comparing schematics against the dts gets easier.
See
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts#n40
for an example
> + vcc5v0_host: vcc5v0-host-regulator {
> + compatible = "regulator-fixed";
> + enable-active-high;
> + regulator-boot-on;
> + gpio = <&gpio4 RK_PD6 GPIO_ACTIVE_HIGH>; // bsp
> + pinctrl-names = "default";
> + pinctrl-0 = <&vcc5v0_host_en>;
> + regulator-name = "vcc5v0_host";
> + // regulator-always-on;
> + vin-supply = <&vcc5v0_sys>;
> + };
> +
> + vcc5v0_typec0: vbus-typec-regulator {
> + compatible = "regulator-fixed";
> + enable-active-high;
> + gpio = <&gpio4 RK_PD2 GPIO_ACTIVE_HIGH>; // bsp
> + pinctrl-names = "default";
> + pinctrl-0 = <&vcc5v0_typec_en>;
> + regulator-name = "vcc5v0_typec0";
> + vin-supply = <&vcc5v0_sys>;
> + };
> +
> + vcc_sys: vcc5v0_sys: vcc5v0-sys { // bsp
> + compatible = "regulator-fixed";
> + regulator-name = "vcc5v0_sys";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + vin-supply = <&dc_12v>;
> + };
> +
> +
double empty line
Thanks
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
ocfox <i@ocfox.me>
Cc: ocfox <i@ocfox.me>
Subject: Re: [PATCH] arm64: dts: rockchip: add support for Rongpin king3399 board
Date: Sat, 01 Jul 2023 13:04:16 +0200 [thread overview]
Message-ID: <4811978.GXAFRqVoOG@diego> (raw)
In-Reply-To: <20230630173010.272469-1-i@ocfox.me>
Hi,
all of what Krzysztof said in his mail + the stuff below please:
Am Freitag, 30. Juni 2023, 19:27:52 CEST schrieb ocfox:
> king3399 is a bord from Rongpin, you can find detail about
> it here:
> (http://www.rpdzkj.com/copy_2_1703937_175104_2536441.html)
>
> This patch add basic node for the board and make it able to bring
> up.
>
> Works:
> - USB, type-C port
> - Ethernet
> - WiFi/BT
> - HDMI
> - eMMC
> - PCIe
> - sd-card
>
> Not test for other peripheral:
> - AUDIO
> - MIC
> - SIM
> - MIPI
>
> Signed-off-by: ocfox <i@ocfox.me>
I think we request a full name here and as patch author.
[...]
> + vcc3v3_sys: vcc3v3-sys {
> + compatible = "regulator-fixed";
> + regulator-name = "vcc3v3_sys";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + vin-supply = <&vcc5v0_sys>;
> + };
> +
> + // 4G Module
please use a consistent comment style ... in the "/* foobar */" style
> + vcc3v3_gsm: vcc3v3-gsm {
> + compatible = "regulator-fixed";
> + enable-active-high;
> + gpio = <&gpio4 RK_PC6 GPIO_ACTIVE_HIGH>; // bsp
> + pinctrl-names = "default";
> + pinctrl-0 = <&vcc3v3_gsm_en>;
> + regulator-name = "vcc3v3_gsm";
> + // regulator-always-on;
> + vin-supply = <&dc_12v>;
> + };
> +
> + // vdd 5v: USB 2&3, USB Hub, Type-C, HDMI, MIPI, IR
so this regulator controls all of those?
In that case maybe do it similarly to vcc1v8-s3 and use multiple labels
for the node - i.e. the line name leading to the consumer from the
schematics.
That way comparing schematics against the dts gets easier.
See
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts#n40
for an example
> + vcc5v0_host: vcc5v0-host-regulator {
> + compatible = "regulator-fixed";
> + enable-active-high;
> + regulator-boot-on;
> + gpio = <&gpio4 RK_PD6 GPIO_ACTIVE_HIGH>; // bsp
> + pinctrl-names = "default";
> + pinctrl-0 = <&vcc5v0_host_en>;
> + regulator-name = "vcc5v0_host";
> + // regulator-always-on;
> + vin-supply = <&vcc5v0_sys>;
> + };
> +
> + vcc5v0_typec0: vbus-typec-regulator {
> + compatible = "regulator-fixed";
> + enable-active-high;
> + gpio = <&gpio4 RK_PD2 GPIO_ACTIVE_HIGH>; // bsp
> + pinctrl-names = "default";
> + pinctrl-0 = <&vcc5v0_typec_en>;
> + regulator-name = "vcc5v0_typec0";
> + vin-supply = <&vcc5v0_sys>;
> + };
> +
> + vcc_sys: vcc5v0_sys: vcc5v0-sys { // bsp
> + compatible = "regulator-fixed";
> + regulator-name = "vcc5v0_sys";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + vin-supply = <&dc_12v>;
> + };
> +
> +
double empty line
Thanks
Heiko
next prev parent reply other threads:[~2023-07-01 11:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 17:27 [PATCH] arm64: dts: rockchip: add support for Rongpin king3399 board ocfox
2023-06-30 17:27 ` ocfox
2023-06-30 17:27 ` ocfox
2023-07-01 9:25 ` Krzysztof Kozlowski
2023-07-01 9:25 ` Krzysztof Kozlowski
2023-07-01 9:25 ` Krzysztof Kozlowski
2023-07-01 11:04 ` Heiko Stübner [this message]
2023-07-01 11:04 ` Heiko Stübner
2023-07-01 11:04 ` Heiko Stübner
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=4811978.GXAFRqVoOG@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=i@ocfox.me \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.