From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Vikash Garodia <quic_vgarodia@quicinc.com>,
Dikshita Agarwal <quic_dikshita@quicinc.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: iris: Be explicit in naming of VPU2 power off handlers
Date: Wed, 2 Jul 2025 17:31:45 +0200 [thread overview]
Message-ID: <246f847a-df24-48a5-ae8c-97fba7f5b3cf@linaro.org> (raw)
In-Reply-To: <dd5717a7-9476-4207-967f-a30e7cb3b3e7@linaro.org>
On 02/07/2025 17:07, Bryan O'Donoghue wrote:
>> {
>> dev_pm_genpd_set_hwmode(core->pmdomain_tbl->pd_devs[IRIS_HW_POWER_DOMAIN], false);
>> iris_disable_power_domains(core, core->pmdomain_tbl->pd_devs[IRIS_HW_POWER_DOMAIN]);
>> diff --git a/drivers/media/platform/qcom/iris/iris_vpu_common.h b/drivers/media/platform/qcom/iris/iris_vpu_common.h
>> index 93b7fa27be3b..8f63f243dd0d 100644
>> --- a/drivers/media/platform/qcom/iris/iris_vpu_common.h
>> +++ b/drivers/media/platform/qcom/iris/iris_vpu_common.h
>> @@ -24,8 +24,8 @@ void iris_vpu_clear_interrupt(struct iris_core *core);
>> int iris_vpu_watchdog(struct iris_core *core, u32 intr_status);
>> int iris_vpu_prepare_pc(struct iris_core *core);
>> int iris_vpu_power_on(struct iris_core *core);
>> -int iris_vpu_power_off_controller(struct iris_core *core);
>> -void iris_vpu_power_off_hw(struct iris_core *core);
>> +int iris_vpu2_power_off_controller(struct iris_core *core);
>> +void iris_vpu2_power_off_hw(struct iris_core *core);
>> void iris_vpu_power_off(struct iris_core *core);
>>
>> #endif
>
> I prefer these names with an explicit v2 more logical/consistent with
> the hw names.
>
> Acked-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Thanks.
I got some patchwork complains, so it seems I missed something which
clang did not catch. There will be a v2.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-02 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 13:42 Krzysztof Kozlowski
2025-07-02 14:02 ` Konrad Dybcio
2025-07-02 14:06 ` Krzysztof Kozlowski
2025-07-02 15:07 ` Bryan O'Donoghue
2025-07-02 15:31 ` Krzysztof Kozlowski [this message]
2025-07-02 17:20 ` Vikash Garodia
2025-07-02 17:29 ` Krzysztof Kozlowski
2025-07-02 17:46 ` 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=246f847a-df24-48a5-ae8c-97fba7f5b3cf@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=abhinav.kumar@linux.dev \
--cc=bryan.odonoghue@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_dikshita@quicinc.com \
--cc=quic_vgarodia@quicinc.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®