[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <59c66b9a-9ced-434e-8e6d-626a1fa70abf@ti.com>
Date: Tue, 28 Jan 2025 11:27:16 +0530
From: Jayesh Choudhary <j-choudhary@...com>
To: Alexander Stein <alexander.stein@...tq-group.com>,
<dri-devel@...ts.freedesktop.org>, <sjakhade@...ence.com>,
<mripard@...nel.org>, <Laurent.pinchart@...asonboard.com>,
<andrzej.hajda@...el.com>, <neil.armstrong@...aro.org>,
<rfoss@...nel.org>
CC: <amishin@...rgos.ru>, <jani.nikula@...el.com>, <tzimmermann@...e.de>,
<maarten.lankhorst@...ux.intel.com>, <jonas@...boo.se>,
<jernej.skrabec@...il.com>, <linux-kernel@...r.kernel.org>,
<devarsht@...com>, Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
Subject: Re: [RFC PATCH] drm: bridge: cdns-mhdp8546: Fix possible null pointer
dereference
Hello Tomi, Alexander,
On 24/01/25 13:38, Alexander Stein wrote:
> Hi,
>
> Am Donnerstag, 23. Januar 2025, 17:20:34 CET schrieb Tomi Valkeinen:
>> Hi,
>>
>> On 16/01/2025 13:16, Jayesh Choudhary wrote:
>>> For the cases we have DRM_BRIDGE_ATTACH_NO_CONNECTOR flag set,
>>
>> Any idea if any other platform than K3 is using this driver? tidss
>> supports DRM_BRIDGE_ATTACH_NO_CONNECTOR, so if K3 is the only user, we
>> could drop the legacy !DRM_BRIDGE_ATTACH_NO_CONNECTOR case. Which would
>> remove quite a bit of code, I think, and make the driver a bit more easy
>> to understand (although I think it could use a major cleanup...).
>
> FYI: Not directly using it, but patch series [1] is at least touching
> this file.
I can't see any other platform using this.
No one uses compatible "cdns,mhdp8546" and only K3 devices uses the
wrapper compatible "ti,j721e-mhdp8546"
Let me post next RFC version with legacy !DRM_BRIDGE_ATTACH_NO_CONNECTOR
dropped.
And the mentioned series only touches mailbox access function to move
then to a common helper file. (So independent change)
>
> Best regards,
> Alexander
>
> [1] https://lore.kernel.org/all/cover.1734340233.git.Sandor.yu@nxp.com/
>
Warm Regards,
Jayesh
Powered by blists - more mailing lists