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: <a0489fea-8c06-4c89-a530-8be691f4705d@ti.com>
Date: Tue, 1 Jul 2025 19:00:09 +0530
From: Devarsh Thakkar <devarsht@...com>
To: Jayesh Choudhary <j-choudhary@...com>, <jyri.sarha@....fi>,
        <maarten.lankhorst@...ux.intel.com>, <mripard@...nel.org>,
        <tzimmermann@...e.de>, <dri-devel@...ts.freedesktop.org>,
        <tomi.valkeinen@...asonboard.com>, <mwalle@...nel.org>
CC: <airlied@...il.com>, <simona@...ll.ch>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/3] Decouple max_pclk check from constant display
 feats

On 01/07/25 15:25, Jayesh Choudhary 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
> correspondig checks using "curr_max_pclk[]".
> 
> 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.
> 

As series is fixing above issue (abnormal behaviour while calling 
clk_round_rate from tidss for VP clock being used by OLDI), can we add 
"Fixes tag" for the patches?

Regards
Devarsh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ