From: Johan Jonker <jbx6244@gmail.com>
To: Alibek Omarov <a1ba.omarov@gmail.com>,
linux-rockchip@lists.infradead.org
Subject: Re: [RFC PATCH 2/3] arm64: dts: rockchip: rk356x: add LVDS bindings
Date: Tue, 31 Jan 2023 14:33:58 +0100 [thread overview]
Message-ID: <f406b303-ff78-33ff-7f59-cc7904b9a9e4@gmail.com> (raw)
In-Reply-To: <20220923160115.2946615-3-a1ba.omarov@gmail.com>
On 9/23/22 18:01, Alibek Omarov wrote:
> Exposes ports for VOP2 and for panel
>
> Signed-off-by: Alibek Omarov <a1ba.omarov@gmail.com>
> ---
> arch/arm64/boot/dts/rockchip/rk356x.dtsi | 25 ++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk356x.dtsi b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> index 0473d7ee2668..fea3319a6a4e 100644
> --- a/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> @@ -787,6 +787,31 @@ hdmi_out: port@1 {
> };
> };
>
> + lvds: lvds {
> + compatible = "rockchip,rk3568-lvds";
Hi Alibek,
1:
In the manufacturer tree they model this node in the grf node.
Any particular reason to do that different?
https://github.com/rockchip-linux/kernel/blob/develop-5.10/arch/arm64/boot/dts/rockchip/rk3568.dtsi#L734
In mainline PX30 already does the same.
2:
There's complete "Acked" serie to be merged by Heiko for a LVDS yaml binding.
[PATCH v6 01/17] dt-bindings: display: rockchip: convert rockchip-lvds.txt to YAML
https://lore.kernel.org/linux-rockchip/67771143-fd83-383d-41b2-68e8707134e8@gmail.com/
Maybe it's better to check this node in a automated way?
Johan
> + clocks = <&cru PCLK_DSITX_0>;
> + clock-names = "pclk_lvds";
> + phys = <&dsi_dphy0>;
> + phy-names = "dphy";
> + power-domains = <&power RK3568_PD_VO>;
> + rockchip,grf = <&grf>;
> + rockchip,output = "lvds";
> + status = "disabled";
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + lvds_in: port@0 {
> + reg = <0>;
> + };
> +
> + lvds_out: port@1 {
> + reg = <1>;
> + };
> + };
> + };
> +
> qos_gpu: qos@fe128000 {
> compatible = "rockchip,rk3568-qos", "syscon";
> reg = <0x0 0xfe128000 0x0 0x20>;
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2023-01-31 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 16:01 [RFC PATCH 0/3] rockchip-lvds for rk3568 Alibek Omarov
2022-09-23 16:01 ` [RFC PATCH 1/3] drm/rockchip: lvds: add rk3568 support Alibek Omarov
2022-09-23 16:01 ` [RFC PATCH 2/3] arm64: dts: rockchip: rk356x: add LVDS bindings Alibek Omarov
2022-11-16 13:19 ` Sverdlin, Alexander
2022-11-16 15:09 ` Alibek Omarov
2022-11-18 18:06 ` Sverdlin, Alexander
2022-11-18 18:52 ` Alibek Omarov
2023-01-31 13:33 ` Johan Jonker [this message]
2023-01-31 18:21 ` Alibek Omarov
2022-09-23 16:01 ` [RFC PATCH 3/3] dt-bindings: display: rockchip-lvds: add compatible string for RK3568 Alibek Omarov
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=f406b303-ff78-33ff-7f59-cc7904b9a9e4@gmail.com \
--to=jbx6244@gmail.com \
--cc=a1ba.omarov@gmail.com \
--cc=linux-rockchip@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