linux-kernel - Re: [PATCH v4 0/3] drm/tidss: Add OLDI bridge support

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 for Android: free password hash cracker in your pocket

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

Message-ID: <86d5d285a8467b3fcdadd3cf37ac0e4cbc874626.camel@siemens.com>
Date: Tue, 25 Mar 2025 18:57:14 +0000
From: "Sverdlin, Alexander" <alexander.sverdlin@...mens.com>
To: "aradhya.bhatia@...ux.dev" <aradhya.bhatia@...ux.dev>
CC: "j-choudhary@...com" <j-choudhary@...com>, "u-kumar1@...com"
	<u-kumar1@...com>, "dri-devel@...ts.freedesktop.org"
	<dri-devel@...ts.freedesktop.org>, "devicetree@...r.kernel.org"
	<devicetree@...r.kernel.org>, "devarsht@...com" <devarsht@...com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "nm@...com"
	<nm@...com>, "vigneshr@...com" <vigneshr@...com>, "praneeth@...com"
	<praneeth@...com>
Subject: Re: [PATCH v4 0/3] drm/tidss: Add OLDI bridge support

Hi Aradhya!

On Thu, 2025-03-20 at 18:54 +0530, Aradhya Bhatia wrote:
> > I've tried to test the patchset with necessary pre-requisites and DT additions
> > with a single channel LVDS pannel and while I'm not successful yet, I've also noticed
> > the following warning:
> > 
> > tidss 30200000.dss: vp0: Clock rate 24285714 differs over 5% from requested 37000000

...

> While you have mentioned that you did add the prerequisites, could you
> confirm that you applied the (now older) dependency patch mentioned in
> the v4 cover-letter[1]?
> Ideally, you should not observe these concerns if [1] were successfully
> applied.
> 
> More importantly, if you are already on latest linux-next, I would
> request you to use v6 of this OLDI series[2], along with the latest
> dependency patches[0], as the older dependency patch is simply not
> applicable on latest kernel anymore! =)

Thanks for all the hints and links! I can confirm that with linux-next and this
time all the necessary dependencies applied, I don't see the above warning.

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com