From: Swamil Jain <s-jain1@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
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>,
<jyri.sarha@iki.fi>, <maarten.lankhorst@linux.intel.com>,
<mripard@kernel.org>, <tzimmermann@suse.de>, <airlied@gmail.com>,
<simona@ffwll.ch>, <aradhya.bhatia@linux.dev>
Subject: Re: [PATCH v6 1/3] drm/tidss: oldi: Add property to identify OLDI supported VP
Date: Wed, 17 Sep 2025 19:02:58 +0530 [thread overview]
Message-ID: <a0df1c72-2571-4791-ac66-07f9b3431ff6@ti.com> (raw)
In-Reply-To: <a306a386-bbd9-408c-b76d-0ecebc1f32ae@ideasonboard.com>
Hi Tomi,
On 9/16/25 17:10, Tomi Valkeinen wrote:
> Hi,
>
> On 11/09/2025 14:07, Swamil Jain wrote:
>> From: Jayesh Choudhary <j-choudhary@ti.com>
>>
>> TIDSS should know which VP has OLDI output to avoid calling clock
>> functions for that VP as those are controlled by oldi driver. Add a
>> property "is_ext_vp_clk" to "tidss_device" structure for that. Mark it
>> 'true' in tidss_oldi_init() and 'false' in tidss_oldi_deinit().
>>
>> Fixes: 7246e0929945 ("drm/tidss: Add OLDI bridge support")
>
> What bug does this fix? It's just adding a new field which it sets to
> true/false...
Please take a look:
https://lore.kernel.org/all/a0489fea-8c06-4c89-a530-8be691f4705d@ti.com/
Should we remove the tag?
Or, else, please suggest a better way to describe the issue mentioned in
above link.
Regards,
Swamil
>
> Tomi
>
>> Tested-by: Michael Walle <mwalle@kernel.org>
>> Reviewed-by: Devarsh Thakkar <devarsht@ti.com>
>> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
>> Signed-off-by: Swamil Jain <s-jain1@ti.com>
>> ---
>> drivers/gpu/drm/tidss/tidss_drv.h | 2 ++
>> drivers/gpu/drm/tidss/tidss_oldi.c | 2 ++
>> 2 files changed, 4 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/tidss/tidss_drv.h b/drivers/gpu/drm/tidss/tidss_drv.h
>> index 84454a4855d1..e1c1f41d8b4b 100644
>> --- a/drivers/gpu/drm/tidss/tidss_drv.h
>> +++ b/drivers/gpu/drm/tidss/tidss_drv.h
>> @@ -24,6 +24,8 @@ struct tidss_device {
>>
>> const struct dispc_features *feat;
>> struct dispc_device *dispc;
>> + bool is_ext_vp_clk[TIDSS_MAX_PORTS];
>> +
>>
>> unsigned int num_crtcs;
>> struct drm_crtc *crtcs[TIDSS_MAX_PORTS];
>> diff --git a/drivers/gpu/drm/tidss/tidss_oldi.c b/drivers/gpu/drm/tidss/tidss_oldi.c
>> index 7688251beba2..7ecbb2c3d0a2 100644
>> --- a/drivers/gpu/drm/tidss/tidss_oldi.c
>> +++ b/drivers/gpu/drm/tidss/tidss_oldi.c
>> @@ -430,6 +430,7 @@ void tidss_oldi_deinit(struct tidss_device *tidss)
>> for (int i = 0; i < tidss->num_oldis; i++) {
>> if (tidss->oldis[i]) {
>> drm_bridge_remove(&tidss->oldis[i]->bridge);
>> + tidss->is_ext_vp_clk[tidss->oldis[i]->parent_vp] = false;
>> tidss->oldis[i] = NULL;
>> }
>> }
>> @@ -580,6 +581,7 @@ int tidss_oldi_init(struct tidss_device *tidss)
>> oldi->bridge.timings = &default_tidss_oldi_timings;
>>
>> tidss->oldis[tidss->num_oldis++] = oldi;
>> + tidss->is_ext_vp_clk[oldi->parent_vp] = true;
>> oldi->tidss = tidss;
>>
>> drm_bridge_add(&oldi->bridge);
>
next prev parent reply other threads:[~2025-09-17 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 11:07 [PATCH v6 0/3] Decouple max_pclk check from constant display feats Swamil Jain
2025-09-11 11:07 ` [PATCH v6 1/3] drm/tidss: oldi: Add property to identify OLDI supported VP Swamil Jain
2025-09-16 11:40 ` Tomi Valkeinen
2025-09-17 13:32 ` Swamil Jain [this message]
2025-09-17 13:48 ` Tomi Valkeinen
2025-09-11 11:07 ` [PATCH v6 2/3] drm/tidss: Remove max_pclk_khz from tidss display features: Swamil Jain
2025-09-16 11:53 ` Tomi Valkeinen
2025-09-16 11:55 ` Tomi Valkeinen
2025-09-11 11:07 ` [PATCH v6 3/3] drm/tidss: oldi: Add atomic_check hook for oldi bridge Swamil Jain
2025-09-15 7:57 ` Maxime Ripard
2025-09-15 8:55 ` Swamil Jain
2025-09-15 10:17 ` Tomi Valkeinen
2025-09-15 12:24 ` Maxime Ripard
2025-09-16 11:58 ` 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=a0df1c72-2571-4791-ac66-07f9b3431ff6@ti.com \
--to=s-jain1@ti.com \
--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=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®