From: "Michael Walle" <mwalle@kernel.org>
To: "Swamil Jain" <s-jain1@ti.com>, <jyri.sarha@iki.fi>,
<tomi.valkeinen@ideasonboard.com>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <airlied@gmail.com>, <simona@ffwll.ch>,
<aradhya.bhatia@linux.dev>
Cc: <h-shenoy@ti.com>, <devarsht@ti.com>, <vigneshr@ti.com>,
<praneeth@ti.com>, <u-kumar1@ti.com>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] Decouple max_pclk check from constant display feats
Date: Thu, 21 Aug 2025 14:09:34 +0200 [thread overview]
Message-ID: <DC83F2197OLI.2KRLEH7GUBKSA@kernel.org> (raw)
In-Reply-To: <20250819192113.2420396-1-s-jain1@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1826 bytes --]
On Tue Aug 19, 2025 at 9:21 PM CEST, Swamil Jain wrote:
> In an effort to make the existing compatibles more usable, we are
> removing the max_pclk_khz form dispc_features structure and doing the
> supported pixel clock checks using "max_successful_rate[]" and
> "max_attempted_rate[]".
>
> Changes are fully backwards compatible.
>
> After integration of OLDI support[0], we need additional patches in
> OLDI to identify the VP that has OLDI. We have to do this since
> OLDI driver owns the VP clock (its serial clock) and we cannot perform
> clock operations on those VP clock from tidss driver. This issue was
> also reported upstream when DSI fixes[1] had some clock related calls
> in tidss driver. When "clk_round_rate()" is called, ideally it should
> have gone to "sci_clk_determine_rate()" to query DM but it doesn't since
> clock is owned by OLDI not tidss.
>
> So add a member is_ext_vp_clk[] in tidss_device structure to identify
> this and avoid performing clock operations for VP if it has OLDI panel.
> For the same checks in OLDI driver, atomic_check() hook is added to its
> bridge_funcs.
> In the atomic_check() chain, first the bridge_atomic_check() is called
> and then crtc_atomic_check() is called. So mode clock is first checked
> in oldi driver and then skipped in tidss driver.
>
> Had the tidss_oldi structure been exposed to tidss_dispc.c, we could
> have directly checked VP type in dispc but since the structure is defined
> in tidss_oldi.c , we have to add additional member to tidss_device
> structure.
>
> [0]: https://lore.kernel.org/all/20250528122544.817829-1-aradhya.bhatia@linux.dev/
> [1]: https://lore.kernel.org/all/DA6TT575Z82D.3MPK8HG5GRL8U@kernel.org/
Since that wasn't picked up from v4:
Tested-by: Michael Walle <mwalle@kernel.org> # on am67a
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2025-08-21 12:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 19:21 Swamil Jain
2025-08-19 19:21 ` [PATCH v5 1/3] drm/tidss: oldi: Add property to identify OLDI supported VP Swamil Jain
2025-08-19 19:21 ` [PATCH v5 2/3] drm/tidss: Remove max_pclk_khz from tidss display features Swamil Jain
2025-08-27 8:49 ` Tomi Valkeinen
2025-08-27 9:27 ` Maxime Ripard
2025-08-27 9:49 ` Tomi Valkeinen
2025-08-27 10:34 ` Maxime Ripard
2025-08-27 10:39 ` Tomi Valkeinen
2025-08-27 11:25 ` Maxime Ripard
2025-08-29 3:37 ` Swamil Jain
2025-09-03 8:38 ` Swamil Jain
2025-09-03 9:31 ` Tomi Valkeinen
2025-09-03 9:43 ` Swamil Jain
2025-09-09 6:51 ` Maxime Ripard
2025-09-10 10:09 ` Swamil Jain
2025-08-29 3:35 ` Swamil Jain
2025-08-28 16:44 ` Swamil Jain
2025-08-19 19:21 ` [PATCH v5 3/3] drm/tidss: oldi: Add atomic_check hook for oldi bridge Swamil Jain
2025-08-27 9:05 ` Tomi Valkeinen
2025-08-29 3:50 ` Swamil Jain
2025-09-01 8:52 ` Tomi Valkeinen
2025-09-01 8:59 ` Swamil Jain
2025-08-21 12:09 ` Michael Walle [this message]
2025-08-28 15:59 ` [PATCH v5 0/3] Decouple max_pclk check from constant display feats Swamil Jain
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=DC83F2197OLI.2KRLEH7GUBKSA@kernel.org \
--to=mwalle@kernel.org \
--cc=airlied@gmail.com \
--cc=aradhya.bhatia@linux.dev \
--cc=devarsht@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=h-shenoy@ti.com \
--cc=jyri.sarha@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=praneeth@ti.com \
--cc=s-jain1@ti.com \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
--cc=u-kumar1@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
all inboxes | Powered by JetHome®