From: Pranjal Shrivastava <praan@google.com>
To: Zhenhua Huang <quic_zhenhuah@quicinc.com>
Cc: robdclark@gmail.com, will@kernel.org, robin.murphy@arm.com,
joro@8bytes.org, iommu@lists.linux.dev,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, quic_c_gdjako@quicinc.com,
dmitry.baryshkov@linaro.org
Subject: Re: [PATCH 1/1] iommu/arm-smmu-qcom: remove runtime pm enabling for TBU driver
Date: Tue, 13 Aug 2024 07:20:14 +0000 [thread overview]
Message-ID: <ZrsJLqTnq6tG2xp4@google.com> (raw)
In-Reply-To: <cca690c3-916e-43b6-b2a5-eca4f2eb838e@quicinc.com>
On Tue, Aug 13, 2024 at 10:37:33AM +0800, Zhenhua Huang wrote:
>
>
> On 2024/8/12 21:25, Pranjal Shrivastava wrote:
> > On Tue, Jul 30, 2024 at 06:30:43PM +0800, Zhenhua Huang wrote:
> > > TBU driver has no runtime pm support now, adding pm_runtime_enable()
> > > seems to be useless. Remove it.
> > >
> > > Signed-off-by: Zhenhua Huang <quic_zhenhuah@quicinc.com>
> > > ---
> > > drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 6 ------
> > > 1 file changed, 6 deletions(-)
> > >
> > > diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
> > > index 36c6b36ad4ff..aff2fe1fda13 100644
> > > --- a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
> > > +++ b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
> > > @@ -566,7 +566,6 @@ static struct acpi_platform_list qcom_acpi_platlist[] = {
> > > static int qcom_smmu_tbu_probe(struct platform_device *pdev)
> > > {
> > > - struct device *dev = &pdev->dev;
> > > int ret;
> > > if (IS_ENABLED(CONFIG_ARM_SMMU_QCOM_DEBUG)) {
> > > @@ -575,11 +574,6 @@ static int qcom_smmu_tbu_probe(struct platform_device *pdev)
> > > return ret;
> > > }
> > > - if (dev->pm_domain) {
> > > - pm_runtime_set_active(dev);
> > > - pm_runtime_enable(dev);
> >
> > I assumed that this was required to avoid the TBU from being powered
> > down? If so, then I think we shall move it under the
>
> Hi Pranjal,
>
> In my sense, this was giving the TBU ability to power down when
> necessary(through pm callbacks)? While I haven't seen any RPM impl for TBU
> device.. hence having the doubt..
>
> Thanks,
> Zhenhua
Apologies for being unclear. I just meant to ask if there was a reason
to add pm_runtime_set_active & enable in the tbu probe previously? And I
*assumed* that it was to set the device state as RPM_ACTIVE to avoid it
being RPM_SUSPENDED after enabling pm_runtime.
I agree that there are no pm_runtime_suspend/resume calls within the TBU
driver. I'm just trying to understand why was pm_runtime enabled here
earlier (since it's not implemented) in order to ensure that removing it
doesn't cause further troubles?
I see Georgi added it as a part of
https://lore.kernel.org/all/20240704010759.507798-1-quic_c_gdjako@quicinc.com/
But I'm unsure why was it required to fix that bug?
>
> > previous if condition, i.e. CONFIG_ARM_SMMU_QCOM_DEBUG?
> >
> > If not, we can remove it give that the TBU would be powered ON as needed
> >
> > > - }
> > > -
> > > return 0;
> > > }
> > > --
> > > 2.7.4
> > >
> > >
> >
> > Thanks,
> > Pranjal
Thanks,
Pranjal
next prev parent reply other threads:[~2024-08-13 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 10:30 [PATCH 1/1] iommu/arm-smmu-qcom: remove runtime pm enabling for TBU driver Zhenhua Huang
2024-08-12 9:18 ` Zhenhua Huang
2024-08-12 13:25 ` Pranjal Shrivastava
2024-08-13 2:37 ` Zhenhua Huang
2024-08-13 7:20 ` Pranjal Shrivastava [this message]
2024-08-13 7:56 ` Zhenhua Huang
2024-08-13 12:06 ` Georgi Djakov
2024-08-14 6:54 ` Zhenhua Huang
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=ZrsJLqTnq6tG2xp4@google.com \
--to=praan@google.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_c_gdjako@quicinc.com \
--cc=quic_zhenhuah@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).