From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Vikash Garodia <quic_vgarodia@quicinc.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Dikshita Agarwal <quic_dikshita@quicinc.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
Marc Gonzalez <mgonzalez@freebox.fr>,
Pierre-Hugues Husson <phhusson@freebox.fr>,
Hans Verkuil <hverkuil@xs4all.nl>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH] media: venus: Fix MSM8998 frequency table
Date: Wed, 4 Jun 2025 15:00:02 +0200 [thread overview]
Message-ID: <aeda0cf4-fd8a-4f3f-a3ea-922d5b0ceec0@oss.qualcomm.com> (raw)
In-Reply-To: <4504e16a-f4c4-1f68-fa91-d3641a3decbe@quicinc.com>
On 6/4/25 2:35 PM, Vikash Garodia wrote:
>
> On 5/31/2025 5:52 PM, Konrad Dybcio wrote:
>> From: Konrad Dybcio <konrad.dybcio@oss.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@oss.qualcomm.com>
>> ---
>> drivers/media/platform/qcom/venus/core.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/media/platform/qcom/venus/core.c b/drivers/media/platform/qcom/venus/core.c
>> index d305d74bb152d21133c4dfa23805b17274426a5c..2bb514c322692475ed58198e17f906f894d81cf4 100644
>> --- a/drivers/media/platform/qcom/venus/core.c
>> +++ b/drivers/media/platform/qcom/venus/core.c
>> @@ -709,11 +709,11 @@ static const struct venus_resources msm8996_res = {
>> };
>>
>> static const struct freq_tbl msm8998_freq_table[] = {
>> - { 1944000, 465000000 }, /* 4k UHD @ 60 (decode only) */
>> - { 972000, 465000000 }, /* 4k UHD @ 30 */
>> - { 489600, 360000000 }, /* 1080p @ 60 */
>> - { 244800, 186000000 }, /* 1080p @ 30 */
>> - { 108000, 100000000 }, /* 720p @ 30 */
>> + { 1728000, 533000000 }, /* 4k UHD @ 60 (decode only) */
>> + { 1036800, 444000000 }, /* 2k @ 120 */
>> + { 829440, 355200000 }, /* 4k @ 44 */
>> + { 489600, 269330000 },/* 4k @ 30 */
>> + { 108000, 200000000 }, /* 1080p @ 60 */
> What has ideally changed in production SKU which led to this change. Pls add
> this info.
I have no clue what's the root reason for the clock plan change, probably
some hw bugs were ironed out and higher clocks were deemed stable
Konrad
next prev parent reply other threads:[~2025-06-04 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 12:22 [PATCH] media: venus: Fix MSM8998 frequency table Konrad Dybcio
2025-06-01 7:46 ` Dmitry Baryshkov
2025-06-06 11:59 ` Arnaud Vrac
2025-06-06 12:14 ` Vikash Garodia
2025-06-07 9:36 ` Konrad Dybcio
2025-06-07 17:01 ` Arnaud Vrac
2025-06-01 8:55 ` Bryan O'Donoghue
2025-06-04 12:35 ` Vikash Garodia
2025-06-04 13:00 ` Konrad Dybcio [this message]
2025-06-06 11:01 ` Vikash Garodia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aeda0cf4-fd8a-4f3f-a3ea-922d5b0ceec0@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=bryan.odonoghue@linaro.org \
--cc=hverkuil@xs4all.nl \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=mchehab@kernel.org \
--cc=mgonzalez@freebox.fr \
--cc=phhusson@freebox.fr \
--cc=quic_dikshita@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=stanimir.k.varbanov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox