linux-kernel - Re: [PATCH v6 10/12] drm/bridge: cdns-dsi: Move DSI mode check to _atomic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c939bbf4-2cde-4897-8ccd-b8d2420fa9b8@linux.dev>
Date: Mon, 13 Jan 2025 21:14:02 +0530
From: Aradhya Bhatia <aradhya.bhatia@...ux.dev>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
 Laurent Pinchart <laurent.pinchart@...asonboard.com>,
 Andrzej Hajda <andrzej.hajda@...el.com>,
 Neil Armstrong <neil.armstrong@...aro.org>, Robert Foss <rfoss@...nel.org>,
 Jonas Karlman <jonas@...boo.se>, Jernej Skrabec <jernej.skrabec@...il.com>,
 Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
 Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
 David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
 Nishanth Menon <nm@...com>, Vignesh Raghavendra <vigneshr@...com>,
 Devarsh Thakkar <devarsht@...com>, Praneeth Bajjuri <praneeth@...com>,
 Udit Kumar <u-kumar1@...com>, Jayesh Choudhary <j-choudhary@...com>,
 DRI Development List <dri-devel@...ts.freedesktop.org>,
 Linux Kernel List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 10/12] drm/bridge: cdns-dsi: Move DSI mode check to
 _atomic_check()



On 1/13/25 14:43, Dmitry Baryshkov wrote:
> On Sun, Jan 12, 2025 at 12:57:36AM +0530, Aradhya Bhatia wrote:
>> From: Aradhya Bhatia <a-bhatia1@...com>
>>
>> At present, the DSI mode configuration check happens during the
>> _atomic_enable() phase, which is not really the best place for this.
>> Moreover, if the mode is not valid, the driver gives a warning and
>> continues the hardware configuration.
>>
>> Move the DSI mode configuration check to _atomic_check() instead, which
>> can properly report back any invalid mode, before the _enable phase even
>> begins.
>>
>> Signed-off-by: Aradhya Bhatia <a-bhatia1@...com>
>> Signed-off-by: Aradhya Bhatia <aradhya.bhatia@...ux.dev>
>> ---
>>  .../gpu/drm/bridge/cadence/cdns-dsi-core.c    | 87 +++++++++++++++++--
>>  .../gpu/drm/bridge/cadence/cdns-dsi-core.h    |  1 +
>>  2 files changed, 83 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.h b/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.h
>> index 5db5dbbbcaad..b785df45bc59 100644
>> --- a/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.h
>> +++ b/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.h
>> @@ -77,6 +77,7 @@ struct cdns_dsi {
>>  	bool link_initialized;
>>  	bool phy_initialized;
>>  	struct phy *dphy;
>> +	struct cdns_dsi_cfg dsi_cfg;
> 
> Is this still something necessary / useful? I think the point was to
> move dsi_cfg to the state, while this is a non-state struct.

No, this isn't necessary. This is a stray piece of code. Looks like I
missed it. Thank you! I will drop this in the next revision.

Regards
Aradhya

> 
>>  };
>>  
>>  #endif /* !__CDNS_DSI_H__ */
>> -- 
>> 2.34.1
>>
>