From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Chaoyi Chen <kernel@airkyi.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Sandy Huang <hjc@rock-chips.com>,
Andy Yan <andy.yan@rock-chips.com>,
Yubing Zhang <yubing.zhang@rock-chips.com>,
Frank Wang <frank.wang@rock-chips.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Amit Sunil Dhamne <amitsd@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dragan Simic <dsimic@manjaro.org>,
Johan Jonker <jbx6244@gmail.com>,
Diederik de Haas <didi.debian@cknow.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 5/5] arm64: dts: rockchip: rk3399-evb-ind: Add support for DisplayPort
Date: Wed, 16 Jul 2025 09:38:49 +0800 [thread overview]
Message-ID: <91933881-e91e-4e3f-a027-1a28a30823ed@rock-chips.com> (raw)
In-Reply-To: <c62d168b-92b5-44a2-9a9a-402d7f4815a2@kernel.org>
Hi Krzysztof,
On 2025/7/15 19:37, Krzysztof Kozlowski wrote:
> On 15/07/2025 13:24, Chaoyi Chen wrote:
>> /dts-v1/;
>> +#include <dt-bindings/usb/pd.h>
>> #include "rk3399.dtsi"
>>
>> / {
>> @@ -19,6 +20,16 @@ chosen {
>> stdout-path = "serial2:1500000n8";
>> };
>>
>> + vbus_typec: vbus-typec-regulator {
> use consistent naming. How other regulators are called? foo-regulator?
Will fix in v2.
>
>> + compatible = "regulator-fixed";
>> + enable-active-high;
>> + gpio = <&gpio1 RK_PC2 GPIO_ACTIVE_HIGH>;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&vcc5v0_typec0_en>;
>> + regulator-name = "vbus_typec";
>> + vin-supply = <&vcc5v0_sys>;
>> + };
>> +
>> vcc5v0_sys: regulator-vcc5v0-sys {
>> compatible = "regulator-fixed";
>> enable-active-high;
>> @@ -29,6 +40,16 @@ vcc5v0_sys: regulator-vcc5v0-sys {
>> regulator-max-microvolt = <5000000>;
>> regulator-min-microvolt = <5000000>;
>> };
>> +
>> + sound: sound {
>> + compatible = "rockchip,rk3399-gru-sound";
>> + rockchip,cpu = <&i2s0 &spdif>;
>> + };
>> +};
>> +
>> +&cdn_dp {
>> + status = "okay";
>> + phys = <&tcphy0_dp>;
>> };
>>
>> &cpu_b0 {
>> @@ -341,6 +362,66 @@ regulator-state-mem {
>> };
>> };
>>
>> +&i2c4 {
>> + i2c-scl-rising-time-ns = <475>;
>> + i2c-scl-falling-time-ns = <26>;
>> + status = "okay";
>> +
>> + usbc0: fusb302@22 {
> Node names should be generic. See also an explanation and list of
> examples (not exhaustive) in DT specification:
> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
Thank you for the explanation. Will fix in v2.
>
>
>> + compatible = "fcs,fusb302";
>> + reg = <0x22>;
>> + interrupt-parent = <&gpio1>;
>> + interrupts = <RK_PA2 IRQ_TYPE_LEVEL_LOW>;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&usbc0_int>;
>> + vbus-supply = <&vbus_typec>;
>> + status = "okay";
> Why? What disabled it?
Oh, that is redundant. Will drop it in v2.
>
>> +
>> + usb_con: connector {
>> + compatible = "usb-c-connector";
>> + label = "USB-C";
> Best regards,
> Krzysztof
>
>
next prev parent reply other threads:[~2025-07-16 2:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 11:24 [PATCH 0/5] Add Type-C DP support for RK3399 EVB IND board Chaoyi Chen
2025-07-15 11:24 ` [PATCH 1/5] dt-bindings: connector: Add displayport connector for hotplug notify Chaoyi Chen
2025-07-15 11:36 ` Krzysztof Kozlowski
2025-07-15 12:04 ` Dmitry Baryshkov
2025-07-16 1:13 ` Chaoyi Chen
2025-07-15 11:24 ` [PATCH 2/5] dt-bindings: phy: rockchip: rk3399-typec-phy: Support mode/orientation switch Chaoyi Chen
2025-07-15 11:34 ` Krzysztof Kozlowski
2025-07-16 1:18 ` Chaoyi Chen
2025-07-15 11:24 ` [PATCH 3/5] phy: rockchip: phy-rockchip-typec: Add support for Type-C TCPM Chaoyi Chen
2025-07-15 12:05 ` Dmitry Baryshkov
2025-07-16 1:56 ` Chaoyi Chen
2025-07-16 7:39 ` Heiko Stübner
2025-07-16 6:15 ` kernel test robot
2025-07-15 11:24 ` [PATCH 4/5] drm/rockchip: cdn-dp: " Chaoyi Chen
2025-07-15 11:24 ` [PATCH 5/5] arm64: dts: rockchip: rk3399-evb-ind: Add support for DisplayPort Chaoyi Chen
2025-07-15 11:37 ` Krzysztof Kozlowski
2025-07-16 1:38 ` Chaoyi Chen [this message]
2025-07-15 12:11 ` Dmitry Baryshkov
2025-07-15 14:25 ` [PATCH 0/5] Add Type-C DP support for RK3399 EVB IND board Rob Herring (Arm)
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=91933881-e91e-4e3f-a027-1a28a30823ed@rock-chips.com \
--to=chaoyi.chen@rock-chips.com \
--cc=airlied@gmail.com \
--cc=amitsd@google.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsimic@manjaro.org \
--cc=frank.wang@rock-chips.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jbx6244@gmail.com \
--cc=kernel@airkyi.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=vkoul@kernel.org \
--cc=yubing.zhang@rock-chips.com \
/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).