From: Jayesh Choudhary <j-choudhary@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: <vigneshr@ti.com>, <a-bhatia1@ti.com>, <afd@ti.com>,
<rogerq@kernel.org>, <s-vadapalli@ti.com>, <conor+dt@kernel.org>,
<r-ravikumar@ti.com>, <sabiya.d@ti.com>, <kristo@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v10 3/5] arm64: dts: ti: k3-j784s4-main: Add DSS and DP-bridge node
Date: Wed, 4 Oct 2023 16:43:36 +0530 [thread overview]
Message-ID: <395f1670-d9cd-42ed-99f0-8d33bc6164e5@ti.com> (raw)
In-Reply-To: <20230927122437.4a76enao7xqyw7hp@retreat>
On 27/09/23 17:54, Nishanth Menon wrote:
> On 17:41-20230927, Jayesh Choudhary wrote:
>> From: Rahul T R <r-ravikumar@ti.com>
>>
>> Add DSS and DP-bridge node for J784S4 SoC. DSS IP in J784S4 is
>> same as DSS IP in J721E, so same compatible is being used.
>> The DP is Cadence MHDP8546.
>>
>> Signed-off-by: Rahul T R <r-ravikumar@ti.com>
>> [j-choudhary@ti.com: move dss & mhdp node together in main, fix dss node]
>> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
>> Reviewed-by: Aradhya Bhatia <a-bhatia1@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 61 ++++++++++++++++++++++
>> 1 file changed, 61 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
>> index a0e4d8808693..5ae11b0d5d0a 100644
>> --- a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
>> @@ -1772,4 +1772,65 @@ c71_3: dsp@67800000 {
>> firmware-name = "j784s4-c71_3-fw";
>> status = "disabled";
>> };
>> +
>> + mhdp: bridge@a000000 {
>> + compatible = "ti,j721e-mhdp8546";
>> + reg = <0x0 0xa000000 0x0 0x30a00>,
>> + <0x0 0x4f40000 0x0 0x20>;
>> + reg-names = "mhdptx", "j721e-intg";
>> + clocks = <&k3_clks 217 11>;
>> + interrupt-parent = <&gic500>;
>> + interrupts = <GIC_SPI 614 IRQ_TYPE_LEVEL_HIGH>;
>> + power-domains = <&k3_pds 217 TI_SCI_PD_EXCLUSIVE>;
>> + status = "disabled";
>
> Document why disabled.
Okay.
>
>> +
>> + dp0_ports: ports {
>> + };
>
> Document why empty node
I will mention that the remote-endpoint are on the board so all the
properties are defined there together. So keeping it empty here.
Other way could be to add #address-cells and #size-cell here with port
child-node. And its remote end point added in the board file. But node
would still be incomplete here.
Warm Regards,
-Jayesh
>
>> + };
>> +
>> + dss: dss@4a00000 {
>> + compatible = "ti,j721e-dss";
>> + reg = <0x00 0x04a00000 0x00 0x10000>, /* common_m */
>> + <0x00 0x04a10000 0x00 0x10000>, /* common_s0*/
>> + <0x00 0x04b00000 0x00 0x10000>, /* common_s1*/
>> + <0x00 0x04b10000 0x00 0x10000>, /* common_s2*/
>> + <0x00 0x04a20000 0x00 0x10000>, /* vidl1 */
>> + <0x00 0x04a30000 0x00 0x10000>, /* vidl2 */
>> + <0x00 0x04a50000 0x00 0x10000>, /* vid1 */
>> + <0x00 0x04a60000 0x00 0x10000>, /* vid2 */
>> + <0x00 0x04a70000 0x00 0x10000>, /* ovr1 */
>> + <0x00 0x04a90000 0x00 0x10000>, /* ovr2 */
>> + <0x00 0x04ab0000 0x00 0x10000>, /* ovr3 */
>> + <0x00 0x04ad0000 0x00 0x10000>, /* ovr4 */
>> + <0x00 0x04a80000 0x00 0x10000>, /* vp1 */
>> + <0x00 0x04aa0000 0x00 0x10000>, /* vp1 */
>> + <0x00 0x04ac0000 0x00 0x10000>, /* vp1 */
>> + <0x00 0x04ae0000 0x00 0x10000>, /* vp4 */
>> + <0x00 0x04af0000 0x00 0x10000>; /* wb */
>> + reg-names = "common_m", "common_s0",
>> + "common_s1", "common_s2",
>> + "vidl1", "vidl2","vid1","vid2",
>> + "ovr1", "ovr2", "ovr3", "ovr4",
>> + "vp1", "vp2", "vp3", "vp4",
>> + "wb";
>> + clocks = <&k3_clks 218 0>,
>> + <&k3_clks 218 2>,
>> + <&k3_clks 218 5>,
>> + <&k3_clks 218 14>,
>> + <&k3_clks 218 18>;
>> + clock-names = "fck", "vp1", "vp2", "vp3", "vp4";
>> + power-domains = <&k3_pds 218 TI_SCI_PD_EXCLUSIVE>;
>> + interrupts = <GIC_SPI 602 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 603 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 604 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 605 IRQ_TYPE_LEVEL_HIGH>;
>> + interrupt-names = "common_m",
>> + "common_s0",
>> + "common_s1",
>> + "common_s2";
>> + status = "disabled";
>
> Same
>
>> +
>> + dss_ports: ports {
>
> Same
>
>> + };
>> + };
>> };
>> --
>> 2.25.1
>>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-04 11:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 12:11 [PATCH v10 0/5] Enable Display for J784S4 and AM69-SK platform Jayesh Choudhary
2023-09-27 12:11 ` [PATCH v10 1/5] arm64: dts: ti: k3-j784s4-main: Add system controller and SERDES lane mux Jayesh Choudhary
2023-09-27 12:11 ` [PATCH v10 2/5] arm64: dts: ti: k3-j784s4-main: Add WIZ and SERDES PHY nodes Jayesh Choudhary
2023-09-27 12:25 ` Nishanth Menon
2023-10-04 11:04 ` Jayesh Choudhary
2023-09-27 12:11 ` [PATCH v10 3/5] arm64: dts: ti: k3-j784s4-main: Add DSS and DP-bridge node Jayesh Choudhary
2023-09-27 12:24 ` Nishanth Menon
2023-10-04 11:13 ` Jayesh Choudhary [this message]
2023-09-27 12:11 ` [PATCH v10 4/5] arm64: dts: ti: k3-j784s4-evm: Enable DisplayPort-0 Jayesh Choudhary
2023-09-27 12:11 ` [PATCH v10 5/5] arm64: dts: ti: k3-am69-sk: Add DP and HDMI support Jayesh Choudhary
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=395f1670-d9cd-42ed-99f0-8d33bc6164e5@ti.com \
--to=j-choudhary@ti.com \
--cc=a-bhatia1@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=r-ravikumar@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=sabiya.d@ti.com \
--cc=vigneshr@ti.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