From: "Renjiang Han (QUIC)" <quic_renjiang@quicinc.com>
To: "dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>
Cc: "bryan.odonoghue@linaro.org" <bryan.odonoghue@linaro.org>,
"Taniya Das (QUIC)" <quic_tdas@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
"Vikash Garodia (QUIC)" <quic_vgarodia@quicinc.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: RE: [PATCH 1/2] clk: qcom: videocc: Use HW_CTRL_TRIGGER flag for video GDSC's
Date: Mon, 25 Nov 2024 15:14:27 +0000 [thread overview]
Message-ID: <7765000a0f87447e98d827dee5977ca7@quicinc.com> (raw)
In-Reply-To: <CAA8EJpqYSujKXPFkdWcqRpOKZ+dJHQDkYM33Mt5JxuA=Mfs+WQ@mail.gmail.com>
On Monday, November 25, 2024 9:55 PM, Dmitry Baryshkov wrote:
> On Mon, 25 Nov 2024 at 07:31, Renjiang Han (QUIC) <quic_renjiang@quicinc.com> wrote:
> > On Saturday, November 23, 2024 8:17 AM, Bryan O'Donoghue wrote:
> > > On 23/11/2024 00:05, Dmitry Baryshkov wrote:
> > > > This leaves sm7150, sm8150 and sm8450 untouched. Don't they also
> > > > need to use HW_CTRL_TRIGGER?
> >
> > > I believe the correct list here is anything that is HFI_VERSION_4XX
> > > in
> >
> > > You can't apply the second patch in this series without ensuring the
> > > clock controllers for sdm845 and sm7180
> >
> > > grep HFI_VERSION_4XX drivers/media/platform/qcom/venus/core.c
> >
> > > drivers/clk/qcom/videocc-sdm845.c
> > > drivers/clk/qcom/videocc-sc7180.c
> >
> > > Hmm.. that's what this patch does, to be fair my other email was flippant.
> >
> > > This is fine in general, once we can get some Tested-by: for it.
> >
> > > That's my question - what platforms has this change been tested on ?
> >
> > > I can do sdm845 but, we'll need to find someone with 7180 to verify IMO.
> >
> > Thanks for your comment. We have run video case with these two patches on sc7180. The result is fine.
> A single case, a thorough tests, a mixture of suspend&resume while playing video cases?
> Also, can I please reiterate my question: sm7150, sm8150 and sm8450 ?
> Should they also be changed to use HW_CTRL_TRIGGER?
> Next question, sdm660, msm8996, msm8998: do they support HW_CTRL_TRIGGER?
Thanks for your review. The video playback and recording cases include video
pause and resume, and full video playback. The results are fine.
Also, this change is only for v4 core (HFI_VERSION_4XX ). Therefore, we have only tested it
on platforms using v4 core. We have not tried other platforms.
sm7150, sm8150 and sm8450 should not use venus v4 core. So they needn't to use HW_CTRL_TRIGGER.
Best Regards,
Renjiang
next prev parent reply other threads:[~2024-11-25 15:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 10:31 [PATCH 0/2] Use APIs in gdsc genpd to switch gdsc mode for venus v4 core Renjiang Han
2024-11-22 10:31 ` [PATCH 1/2] clk: qcom: videocc: Use HW_CTRL_TRIGGER flag for video GDSC's Renjiang Han
2024-11-22 10:59 ` Dmitry Baryshkov
2024-11-22 16:55 ` Taniya Das
2024-11-23 0:05 ` Dmitry Baryshkov
2024-11-23 0:16 ` Bryan O'Donoghue
2024-11-25 5:31 ` Renjiang Han (QUIC)
2024-11-25 13:55 ` Dmitry Baryshkov
2024-11-25 15:14 ` Renjiang Han (QUIC) [this message]
2024-11-25 16:27 ` Dmitry Baryshkov
2024-12-18 11:26 ` Renjiang Han
2024-11-26 4:04 ` Taniya Das
2024-11-26 7:37 ` Dmitry Baryshkov
2024-11-22 10:31 ` [PATCH 2/2] venus: pm_helpers: Use dev_pm_genpd_set_hwmode to switch GDSC mode on V4 Renjiang Han
2024-11-22 12:50 ` Bryan O'Donoghue
2024-11-25 3:34 ` Renjiang Han (QUIC)
2024-11-23 0:18 ` [PATCH 0/2] Use APIs in gdsc genpd to switch gdsc mode for venus v4 core Bryan O'Donoghue
2024-11-25 3:49 ` Renjiang Han (QUIC)
2024-11-25 9:35 ` Bryan O'Donoghue
2024-11-25 10:13 ` Renjiang Han (QUIC)
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=7765000a0f87447e98d827dee5977ca7@quicinc.com \
--to=quic_renjiang@quicinc.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=sboyd@kernel.org \
--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