mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aradhya Bhatia <aradhya.bhatia@linux.dev>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.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>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
	Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	Swamil Jain <s-jain1@ti.com>, Devarsh Thakkar <devarsht@ti.com>,
	Louis Chauvet <louis.chauvet@bootlin.com>
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 12/14] drm/tidss: Add support for AM62P display subsystem
Date: Mon, 2 Nov 2026 14:02:13 +0000	[thread overview]
Message-ID: <5782a7a2-3fb4-4d74-aae9-e1ff0d0d4393@linux.dev> (raw)
In-Reply-To: <20261029-beagley-ai-display-v4-12-dc7f2b532478@ideasonboard.com>

Hi Tomi,

On 29/10/26 10:18, Tomi Valkeinen wrote:
> From: Swamil Jain <s-jain1@ti.com>
> 
> The DSS controller on TI's AM62P SoC features two instances of the TI
> DSS. Each DSS instance supports two video ports, similar to the DSS
> controller found on the TI AM62X SoC. This allows three independent
> video streams to be supported: OLDI, DPI, and DSI.
> 
> Since the DSS instances on AM62P are architecturally similar to those
> on the AM62X DSS controller, the existing dispc_am625_feats
> configuration can be reused for the AM62P DSS support.
> 
> This commit adds the necessary device tree compatibility entry for
> "ti,am62p-dss" in the tidss driver, pointing to dispc_am625_feats,
> thereby enabling DSS support on AM62P devices.
> 
> Signed-off-by: Swamil Jain <s-jain1@ti.com>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>

Reviewed-by: Aradhya Bhatia <aradhya.bhatia@linux.dev>

> ---
>  drivers/gpu/drm/tidss/tidss_drv.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/tidss/tidss_drv.c b/drivers/gpu/drm/tidss/tidss_drv.c
> index 44b0b009c29a..8e3cbfb5ef87 100644
> --- a/drivers/gpu/drm/tidss/tidss_drv.c
> +++ b/drivers/gpu/drm/tidss/tidss_drv.c
> @@ -240,6 +240,7 @@ static const struct of_device_id tidss_of_table[] = {
>  	{ .compatible = "ti,am625-dss", .data = &dispc_am625_feats, },
>  	{ .compatible = "ti,am62a7-dss", .data = &dispc_am62a7_feats, },

On a separate note,

Now that `vp_bus_type` support has been dropped, the only thing
different `dispc_am62a7_feats` has from `dispc_am625_feats` is the
subrev macro.

The DSS in AM62A7 SoC is functionally same with that in AM625 SoC; the
only difference being the absence of both the OLDI TXes in AM62A7.

The dt-bindings enforce that rule.

The only place subrev DISPC_AM625 is used, and subrev DISPC_AM62A7 is
not, is for an OLDI reset done log print.

if (dispc->feat->subrev == DISPC_AM625 ||
    dispc->feat->subrev == DISPC_AM65X)
	dev_dbg(dispc->dev, "OLDI RESETDONE %d,%d,%d\n",
		REG_GET(dispc, DSS_SYSSTATUS, GENMASK(5, 5)),
		REG_GET(dispc, DSS_SYSSTATUS, GENMASK(6, 6)),
		REG_GET(dispc, DSS_SYSSTATUS, GENMASK(7, 7)));

Should we consider some workaround for this print, so that we can
entirely drop `dispc_am62a7_feats`?


--
Regards
Aradhya


  reply	other threads:[~2026-11-02 14:02 UTC|newest]

Thread overview: 30+ 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-11-01 13:49   ` Aradhya Bhatia
2026-10-29 10:18 ` [PATCH v4 02/14] drm/tidss: Add helper to identify the AM65x OLDI video port Tomi Valkeinen
2026-11-01 13:50   ` Aradhya Bhatia
2026-10-29 10:18 ` [PATCH v4 03/14] drm/tidss: Stop using vp_bus_type for directly connected panels Tomi Valkeinen
2026-11-01 14:07   ` Aradhya Bhatia
2026-10-29 10:18 ` [PATCH v4 04/14] drm/tidss: Drop the tied off video port check from mode validation Tomi Valkeinen
2026-11-01 14:07   ` Aradhya Bhatia
2026-10-29 10:18 ` [PATCH v4 05/14] drm/tidss: Remove the unused vp_bus_type feat Tomi Valkeinen
2026-11-01 14:09   ` Aradhya Bhatia
2026-10-29 10:18 ` [PATCH v4 06/14] drm/tidss: oldi: Drop unnecessary forward declaration Tomi Valkeinen
2026-11-01 14:11   ` Aradhya Bhatia
2026-11-02 11:41     ` 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-11-01 14:17   ` Aradhya Bhatia
2026-10-29 10:18 ` [PATCH v4 08/14] drm/tidss: oldi: Fix serial clock reference leak Tomi Valkeinen
2026-11-01 14:17   ` Aradhya Bhatia
2026-10-29 10:18 ` [PATCH v4 09/14] drm/tidss: oldi: Fix cleanup on a failed init Tomi Valkeinen
2026-11-01 14:14   ` Aradhya Bhatia
2026-11-02 11:46     ` Tomi Valkeinen
2026-11-02 13:30       ` Aradhya Bhatia
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-11-02 13:31   ` Aradhya Bhatia
2026-10-29 10:18 ` [PATCH v4 11/14] drm/tidss: oldi: Add power domain support Tomi Valkeinen
2026-11-02 13:45   ` Aradhya Bhatia
2026-10-29 10:18 ` [PATCH v4 12/14] drm/tidss: Add support for AM62P display subsystem Tomi Valkeinen
2026-11-02 14:02   ` Aradhya Bhatia [this message]
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: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=5782a7a2-3fb4-4d74-aae9-e1ff0d0d4393@linux.dev \
    --to=aradhya.bhatia@linux.dev \
    --cc=airlied@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devarsht@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=louis.chauvet@bootlin.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=s-jain1@ti.com \
    --cc=simona@ffwll.ch \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=tzimmermann@suse.de \
    --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

all inboxes | Powered by JetHome®