From: Vignesh Raghavendra <vigneshr@ti.com>
To: Rahul T R <r-ravikumar@ti.com>, <nm@ti.com>
Cc: <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski@canonical.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tomi.valkeinen@ideasonboard.com>,
<laurent.pinchart@ideasonboard.com>, <kishon@ti.com>
Subject: Re: [PATCH v3 0/2] DSS: Add support for DisplayPort
Date: Fri, 15 Apr 2022 12:51:12 +0530 [thread overview]
Message-ID: <ed64bf63-95c6-94ae-4c4f-a206250f44a9@ti.com> (raw)
In-Reply-To: <20220406165852.13026-1-r-ravikumar@ti.com>
On 06/04/22 10:28 pm, Rahul T R wrote:
> The following series of patches enables DisplayPort on
> j721e-evm
>
> Tomi Valkeinen (2):
> arm64: dts: ti: k3-j721e-main: add DP & DP PHY
> arm64: dts: ti: k3-j721e-common-proc-board: add DP to j7 evm
>
> v2:
> - use phandle with a parameter to refer clocks insted of
> sub nodes in serdes_wiz node
> - move phy link node to board DTS file
>
> v3:
> - Fix the regulator node name as per the DT spec
> - Use Macro for GPIO type
>
> boot logs:
> https://gist.githubusercontent.com/ravi-rahul/1bdbc3f77ab381e486c8394650c2e85d/raw/f04584c30181821c4ee83aee7781a9ba143cd3f3/j7_DP_upstream.log
>
> kernel patch verify report:
> https://gist.githubusercontent.com/ravi-rahul/a982fef3fae03ec0dbdd5cb475a4cb25/raw/c8230370746e9878daf9527c3aa9d82eed7aa33c/report-kernel-patch-verify.txt
Hmm, With dtbs_check I see (on v5.18-rc1 tag)
+/workdir/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dtb: dp-bridge@a000000: ports: 'port@0' is a required property
+/workdir/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dtb: dp-bridge@a000000: ports: 'port@4' is a required property
+/workdir/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dtb: dp-bridge@a000000: 'phys' is a required property
+/workdir/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dtb: dp-bridge@a000000: 'phy-names' is a required property
This goes away with 2/2 although adds:
+<stdout>: Warning (graph_child_address): /bus@100000/dss@4a00000/ports: graph node has single child node 'port@0', #address-cells/#size-cells are not necessary
Do we need to have empty ports node in j721e-main.dtsi for dp-bridge? And something similar wrt phys as well?
Regards
Vignesh
>
> .../dts/ti/k3-j721e-common-proc-board.dts | 78 ++++++++++++++++++-
> arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 65 ++++++++++++++++
> 2 files changed, 139 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2022-04-15 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 16:58 Rahul T R
2022-04-06 16:58 ` [PATCH v3 1/2] arm64: dts: ti: k3-j721e-main: add DP & DP PHY Rahul T R
2022-04-15 7:27 ` Vignesh Raghavendra
2022-04-06 16:58 ` [PATCH v3 2/2] arm64: dts: ti: k3-j721e-common-proc-board: add DP to j7 evm Rahul T R
2022-04-15 7:21 ` Vignesh Raghavendra [this message]
2022-04-22 14:16 ` [PATCH v3 0/2] DSS: Add support for DisplayPort Rahul T R
2022-04-22 16:17 ` Nishanth Menon
2022-04-26 14:56 ` Rahul T R
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=ed64bf63-95c6-94ae-4c4f-a206250f44a9@ti.com \
--to=vigneshr@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=laurent.pinchart@ideasonboard.com \
--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=tomi.valkeinen@ideasonboard.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
all inboxes | Powered by JetHome®