linux-kernel - Re: [PATCH] media: venus: Fix MSM8998 frequency table

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] [day] [month] [year] [list]

Message-ID: <CAN5H-g7uxH2sqxXdzE-BQtLXYgaEg+h7A=9kuKqwdAZEMXp4Zw@mail.gmail.com>
Date: Sat, 7 Jun 2025 19:01:07 +0200
From: Arnaud Vrac <rawoul@...il.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: Vikash Garodia <quic_vgarodia@...cinc.com>, 
	Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>, Konrad Dybcio <konradybcio@...nel.org>, 
	Dikshita Agarwal <quic_dikshita@...cinc.com>, "Bryan O'Donoghue" <bryan.odonoghue@...aro.org>, 
	Mauro Carvalho Chehab <mchehab@...nel.org>, Stanimir Varbanov <stanimir.k.varbanov@...il.com>, 
	Marc Gonzalez <mgonzalez@...ebox.fr>, Pierre-Hugues Husson <phhusson@...ebox.fr>, 
	Hans Verkuil <hverkuil@...all.nl>, Marijn Suijten <marijn.suijten@...ainline.org>, 
	linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] media: venus: Fix MSM8998 frequency table

Le sam. 7 juin 2025 à 11:36, Konrad Dybcio
<konrad.dybcio@....qualcomm.com> a écrit :
>
> On 6/6/25 2:14 PM, Vikash Garodia wrote:
> > Hi,
> >
> > On 6/6/2025 5:29 PM, Arnaud Vrac wrote:
> >> Le dim. 1 juin 2025 à 09:46, Dmitry Baryshkov
> >> <dmitry.baryshkov@....qualcomm.com> a écrit :
> >>>
> >>> On Sat, May 31, 2025 at 02:22:00PM +0200, Konrad Dybcio wrote:
> >>>> From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
> >>>>
> >>>> Fill in the correct data for the production SKU.
> >>>>
> >>>> Fixes: 193b3dac29a4 ("media: venus: add msm8998 support")
> >>>> Signed-off-by: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
> >>>> ---
> >>>>  drivers/media/platform/qcom/venus/core.c | 10 +++++-----
> >>>>  1 file changed, 5 insertions(+), 5 deletions(-)
> >>>>
> >>>
> >>> Verified against msm-4.4
> >>
> >> Hello,
> >>
> >> The current values are based on
> >> https://git.codelinaro.org/clo/la/kernel/msm-4.4/-/blob/caf_migration/kernel.lnx.4.4.r38-rel/arch/arm/boot/dts/qcom/msm8998-vidc.dtsi
> >> which we've been using in production for many years.
> >
> > I see -v2 updates these to 533/444/.. MHz [1]. If the value changes based on
> > board variants, these need to be picked from board DT instead of driver then.
>
> I believe they don't (although there exist some SoCs where fuses determine
> maximum frequency for a given target). We really want to move off of in-driver
> freq tables but that is still in progress.
>
> >
> > [1]
> > https://git.codelinaro.org/clo/la/kernel/msm-4.4/-/blob/caf_migration/kernel.lnx.4.4.r38-rel/arch/arm/boot/dts/qcom/msm8998-v2.dtsi#L1140
>
> Arnaud, as Vikash mentioned, dvfs tables and some other magic values may
> get overriden in socname-v2/-v2.1/v3 etc. I'm not a fan that downstream
> leaves irrelevant information for old revisions in place, instead of
> simply replacing them, but what can I do..
>
> Unless you somehow came into posession of v1 SoCs (which I believe were
> totally internal), your hw has not been stretching its legs fully for
> all this time.
>

Yes, I missed that the values were overridden in the msm8998-v2.dtsi
file, sorry for the confusion.

-Arnaud