mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Taniya Das <quic_tdas@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Renjiang Han <quic_renjiang@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_vgarodia@quicinc.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	<linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
	<linux-kernel@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: Tue, 26 Nov 2024 09:34:12 +0530	[thread overview]
Message-ID: <5be1ca54-6a9c-46da-81cc-882ae1596cae@quicinc.com> (raw)
In-Reply-To: <23ho25gl3iwyi2jspb6a2x5bv76fco5pkg2x5ct4gu3c44dbiq@yec6evx5sihm>



On 11/23/2024 5:35 AM, Dmitry Baryshkov wrote:
> On Fri, Nov 22, 2024 at 10:25:44PM +0530, Taniya Das wrote:
>>
>>
>> On 11/22/2024 4:29 PM, Dmitry Baryshkov wrote:
>>> On Fri, Nov 22, 2024 at 04:01:45PM +0530, Renjiang Han wrote:
>>>> From: Taniya Das <quic_tdas@quicinc.com>
>>>>
>>>> The video driver will be using the newly introduced
>>>
>>> 'will be' or 'is using'? Or will be using it for these platforms? Is
>>> there any kind of dependency between two patches in the series?
>>>
>> The video driver will not be able to work without the clock side changes.
> 
> Will enabling this flag break the video driver until it is updated?
> 

Yes, my understanding is yes it will break. When we first introduced the 
flag we had got the driver and the clock changes together.

>>
>>>> dev_pm_genpd_set_hwmode() API to switch the video GDSC to HW and SW
>>>> control modes at runtime.
>>>> Hence use HW_CTRL_TRIGGER flag instead of HW_CTRL for video GDSC's for
>>>> Qualcomm SoC SC7180 and SDM845.
>>>
>>> Is it applicable to any other platforms? Why did you select just these
>>> two?
>>>
>>
>> The V6 version of Video driver is already using them, now the video driver
>> wants to migrate to v4 version of the HW to use the new flag.
> 
> I mean slightly different issue. We have following drivers:
> 
> videocc-sa8775p.c - already uses HW_CTRL_TRIGGER
> videocc-sc7180.c - being converted now
> videocc-sc7280.c - already uses HW_CTRL_TRIGGER
> videocc-sdm845.c - being converted now
> videocc-sm7150.c
> videocc-sm8150.c
> videocc-sm8250.c - already uses HW_CTRL_TRIGGER
> videocc-sm8350.c - already uses HW_CTRL_TRIGGER
> videocc-sm8450.c
> videocc-sm8550.c - already uses HW_CTRL_TRIGGER
> 
> This leaves sm7150, sm8150 and sm8450 untouched. Don't they also need to
> use HW_CTRL_TRIGGER?
> 

Yes, I am okay to add the flag, but looking for the Video SW team to 
confirm they are well tested on the rest of the platforms.

>>
>>>>
>>>> Signed-off-by: Taniya Das <quic_tdas@quicinc.com>
>>>> Signed-off-by: Renjiang Han <quic_renjiang@quicinc.com>
>>>> ---
>>>>    drivers/clk/qcom/videocc-sc7180.c | 2 +-
>>>>    drivers/clk/qcom/videocc-sdm845.c | 4 ++--
>>>>    2 files changed, 3 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/drivers/clk/qcom/videocc-sc7180.c b/drivers/clk/qcom/videocc-sc7180.c
>>>> index d7f84548039699ce6fdd7c0f6675c168d5eaf4c1..dd2441d6aa83bd7cff17deeb42f5d011c1e9b134 100644
>>>> --- a/drivers/clk/qcom/videocc-sc7180.c
>>>> +++ b/drivers/clk/qcom/videocc-sc7180.c
>>>> @@ -166,7 +166,7 @@ static struct gdsc vcodec0_gdsc = {
>>>>    	.pd = {
>>>>    		.name = "vcodec0_gdsc",
>>>>    	},
>>>> -	.flags = HW_CTRL,
>>>> +	.flags = HW_CTRL_TRIGGER,
>>>>    	.pwrsts = PWRSTS_OFF_ON,
>>>>    };
>>>> diff --git a/drivers/clk/qcom/videocc-sdm845.c b/drivers/clk/qcom/videocc-sdm845.c
>>>> index f77a0777947773dc8902c92098acff71b9b8f10f..6dedc80a8b3e18eca82c08a5bcd7e1fdc374d4b5 100644
>>>> --- a/drivers/clk/qcom/videocc-sdm845.c
>>>> +++ b/drivers/clk/qcom/videocc-sdm845.c
>>>> @@ -260,7 +260,7 @@ static struct gdsc vcodec0_gdsc = {
>>>>    	},
>>>>    	.cxcs = (unsigned int []){ 0x890, 0x930 },
>>>>    	.cxc_count = 2,
>>>> -	.flags = HW_CTRL | POLL_CFG_GDSCR,
>>>> +	.flags = HW_CTRL_TRIGGER | POLL_CFG_GDSCR,
>>>>    	.pwrsts = PWRSTS_OFF_ON,
>>>>    };
>>>> @@ -271,7 +271,7 @@ static struct gdsc vcodec1_gdsc = {
>>>>    	},
>>>>    	.cxcs = (unsigned int []){ 0x8d0, 0x950 },
>>>>    	.cxc_count = 2,
>>>> -	.flags = HW_CTRL | POLL_CFG_GDSCR,
>>>> +	.flags = HW_CTRL_TRIGGER | POLL_CFG_GDSCR,
>>>>    	.pwrsts = PWRSTS_OFF_ON,
>>>>    };
>>>>
>>>> -- 
>>>> 2.34.1
>>>>
>>>
>>
>> -- 
>> Thanks & Regards,
>> Taniya Das.
> 

-- 
Thanks & Regards,
Taniya Das.

  parent reply	other threads:[~2024-11-26  4:04 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)
2024-11-25 16:27                 ` Dmitry Baryshkov
2024-12-18 11:26                   ` Renjiang Han
2024-11-26  4:04         ` Taniya Das [this message]
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=5be1ca54-6a9c-46da-81cc-882ae1596cae@quicinc.com \
    --to=quic_tdas@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_renjiang@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

all inboxes | Powered by JetHome®