From: sashiko-bot@kernel.org
To: "Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 13/14] arm64: dts: ti: k3-am62p-j722s-common-main: Add support for DSS
Date: Thu, 29 Oct 2026 10:28:28 +0000 [thread overview]
Message-ID: <sashiko-outbox-189132@kernel.org> (raw)
In-Reply-To: <20261029-beagley-ai-display-v4-13-dc7f2b532478@ideasonboard.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] arm64: dts: ti: missing cbass_main ranges for DSS1, DSI0, and DPHY on AM62P
--
commit c11e92d40644178d0a46e3ee6a4f0ebbf85859f3
Author: Jayesh Choudhary <j-choudhary@ti.com>
arm64: dts: ti: k3-am62p-j722s-common-main: Add support for DSS
This commit adds device tree nodes for DSS0, DSS1, OLDI0, OLDI1, DPHY, and
DSI to the shared k3-am62p-j722s-common-main.dtsi file along with the fixed
factor OLDI pixel clock dividers in k3-am62p.dtsi and k3-j722s.dtsi.
> diff --git a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
> index f130c7cb998d7..ae8db1bccadd5 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
[ ... ]
> @@ -1111,6 +1116,63 @@ dphy0: phy@30110000 {
> status = "disabled";
> };
>
> + dphy_tx0: phy@301c0000 {
> + compatible = "ti,j721e-dphy";
> + reg = <0x0 0x301c0000 0x0 0x1000>;
[ ... ]
> + };
[ ... ]
> @@ -1119,6 +1181,54 @@ vpu: video-codec@30210000 {
> power-domains = <&k3_pds 204 TI_SCI_PD_EXCLUSIVE>;
> };
>
> + dss1: dss@30220000 {
> + compatible = "ti,am62p-dss";
> + reg = <0x00 0x30220000 0x00 0x1000>, /* common */
> + <0x00 0x30222000 0x00 0x1000>, /* vidl1 */
> + <0x00 0x30226000 0x00 0x1000>, /* vid */
> + <0x00 0x30227000 0x00 0x1000>, /* ovr1 */
> + <0x00 0x30228000 0x00 0x1000>, /* ovr2 */
> + <0x00 0x3022a000 0x00 0x1000>, /* vp1: Used for DPI/OLDI */
> + <0x00 0x3022b000 0x00 0x1000>, /* vp2: Used for DPI/DSI */
> + <0x00 0x30221000 0x00 0x1000>; /* common1 */
[ ... ]
> + };
> +
> + dsi0: dsi@30500000 {
> + compatible = "ti,j721e-dsi";
> + reg = <0x0 0x30500000 0x0 0x100000>, <0x0 0x30270000 0x0 0x100>;
[Severity: High]
Are the cbass_main bus ranges in arch/arm64/boot/dts/ti/k3-am62p.dtsi
missing entries for dphy_tx0, dss1, and dsi0?
The nodes dphy_tx0 (0x301c0000), dss1 (0x30220000), and dsi0 (0x30500000
and 0x30270000) are added under cbass_main in
arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi.
While arch/arm64/boot/dts/ti/k3-j722s.dtsi defines ranges in cbass_main
for all of these regions:
<0x00 0x301c0000 0x00 0x301c0000 0x00 0x00001000>, /* DPHY-TX */
<0x00 0x30101000 0x00 0x30101000 0x00 0x00080100>, /* CSI window */
<0x00 0x30200000 0x00 0x30200000 0x00 0x00010000>, /* DSS */
<0x00 0x30210000 0x00 0x30210000 0x00 0x00010000>, /* VPU */
<0x00 0x30220000 0x00 0x30220000 0x00 0x00010000>, /* DSS1 */
<0x00 0x30270000 0x00 0x30270000 0x00 0x00010000>, /* DSI-base1 */
<0x00 0x30500000 0x00 0x30500000 0x00 0x00100000>, /* DSI-base2 */
arch/arm64/boot/dts/ti/k3-am62p.dtsi only has the range for DSS0
(0x30200000) and VPU (0x30210000) in cbass_main:
<0x00 0x30040000 0x00 0x30040000 0x00 0x00080000>, /* PRUSS-M */
<0x00 0x30101000 0x00 0x30101000 0x00 0x00010100>, /* CSI window */
<0x00 0x30200000 0x00 0x30200000 0x00 0x00010000>, /* DSS */
<0x00 0x30210000 0x00 0x30210000 0x00 0x00010000>, /* VPU */
<0x00 0x31000000 0x00 0x31000000 0x00 0x00050000>, /* USB0 DWC3 Core window */
When dphy_tx0, dss1, or dsi0 is enabled on an AM62P board, address
translation via of_device_alloc() -> of_address_to_resource() ->
of_translate_address() -> of_translate_one() will fail to find a matching
range in cbass_main, trigger a WARN_ON(rc) in of_device_alloc(), and cause
driver probe to fail when mapping the memory resources.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261029-beagley-ai-display-v4-0-dc7f2b532478@ideasonboard.com?part=13
next prev parent reply other threads:[~2026-10-29 10:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 10:18 [PATCH v4 00/14] drm/tidss: Add BeagleY-AI display support (and some more) Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 01/14] dt-bindings: display: ti,am65x-dss: Add AM62P DSS Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 02/14] drm/tidss: Add helper to identify the AM65x OLDI video port Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 03/14] drm/tidss: Stop using vp_bus_type for directly connected panels Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 04/14] drm/tidss: Drop the tied off video port check from mode validation Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 05/14] drm/tidss: Remove the unused vp_bus_type feat Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 06/14] drm/tidss: oldi: Drop unnecessary forward declaration Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 07/14] drm/tidss: oldi: Fix wrong return value from tidss_oldi_mode_valid() Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 08/14] drm/tidss: oldi: Fix serial clock reference leak Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 09/14] drm/tidss: oldi: Fix cleanup on a failed init Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 10/14] drm/tidss: oldi: Move the setup of one OLDI TX to its own function Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 11/14] drm/tidss: oldi: Add power domain support Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 12/14] drm/tidss: Add support for AM62P display subsystem Tomi Valkeinen
2026-10-29 10:18 ` [PATCH v4 13/14] arm64: dts: ti: k3-am62p-j722s-common-main: Add support for DSS Tomi Valkeinen
2026-10-29 10:28 ` sashiko-bot [this message]
2026-10-29 10:19 ` [PATCH v4 14/14] arm64: dts: ti: beagley-ai: Enable HDMI display and audio Tomi Valkeinen
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=sashiko-outbox-189132@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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 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.