From: Vivek Gautam <vivek.gautam@codeaurora.org>
To: Robin Murphy <robin.murphy@arm.com>, Will Deacon <will.deacon@arm.com>
Cc: Tomasz Figa <tfiga@chromium.org>,
"list@263.net:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Joerg Roedel <joro@8bytes.org>,
joro@8bytes.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"list@263.net:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org, devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Rob Clark <robdclark@gmail.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Sricharan R <sricharan@codeaurora.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Archit Taneja <architt@codeaurora.org>,
Lukas Wunner <lukas@wunner.de>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v11 0/4] iommu/arm-smmu: Add runtime pm/sleep support
Date: Fri, 18 May 2018 15:44:01 +0530 [thread overview]
Message-ID: <8bda01d5-61aa-d163-3b25-e8b055d54644@codeaurora.org> (raw)
In-Reply-To: <CAAFQd5CDY5p8oBz4QC5f6GsKiiYqdenCHGCqKhuWn10JwKjOpw@mail.gmail.com>
Hi Robin,
On 4/9/2018 9:52 AM, Tomasz Figa wrote:
> Hi Will, Robin,
>
> On Thu, Mar 22, 2018 at 7:22 PM Vivek Gautam <vivek.gautam@codeaurora.org>
> wrote:
>
>> This series provides the support for turning on the arm-smmu's
>> clocks/power domains using runtime pm. This is done using the
>> recently introduced device links patches, which lets the smmu's
>> runtime to follow the master's runtime pm, so the smmu remains
>> powered only when the masters use it.
>> As not all implementations support clock/power gating, we are checking
>> for a valid 'smmu->dev's pm_domain' to conditionally enable the runtime
>> power management for such smmu implementations that can support it.
>> This series also adds support for Qcom's arm-smmu-v2 variant that
>> has different clocks and power requirements.
>> Took some reference from the exynos runtime patches [1].
>> With conditional runtime pm now, we avoid touching dev->power.lock
>> in fastpaths for smmu implementations that don't need to do anything
>> useful with pm_runtime.
>> This lets us to use the much-argued pm_runtime_get_sync/put_sync()
>> calls in map/unmap callbacks so that the clients do not have to
>> worry about handling any of the arm-smmu's power.
>> Previous version of this patch series is @ [5].
>> [v11]
>> * Some more cleanups for device link. We don't need an explicit
>> delete for device link from the driver, but just set the flag
>> DL_FLAG_AUTOREMOVE.
>> device_link_add() API description says -
>> "If the DL_FLAG_AUTOREMOVE is set, the link will be removed
>> automatically when the consumer device driver unbinds."
>> * Addressed the comments for 'smmu' in arm_smmu_map/unmap().
>> * Dropped the patch [10] that introduced device_link_del_dev() API.
> As far as I can see, this version addresses all the earlier comments. Do
> you think this is something that you could apply?
>
> Best regards,
> Tomasz
Gentle ping. Are we picking this series for 4.18?
Regards
Vivek
next prev parent reply other threads:[~2018-05-18 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 10:22 Vivek Gautam
2018-03-22 10:22 ` [PATCH v11 1/4] iommu/arm-smmu: Add pm_runtime/sleep ops Vivek Gautam
2018-03-22 10:22 ` [PATCH v11 2/4] iommu/arm-smmu: Invoke pm_runtime during probe, add/remove device Vivek Gautam
2018-03-22 10:22 ` [PATCH v11 3/4] iommu/arm-smmu: Add the device_link between masters and smmu Vivek Gautam
2018-03-22 10:22 ` [PATCH v11 4/4] iommu/arm-smmu: Add support for qcom,smmu-v2 variant Vivek Gautam
2018-04-09 4:22 ` [PATCH v11 0/4] iommu/arm-smmu: Add runtime pm/sleep support Tomasz Figa
2018-05-18 10:14 ` Vivek Gautam [this message]
2018-05-21 13:42 ` Robin Murphy
2018-05-30 10:02 ` Vivek Gautam
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=8bda01d5-61aa-d163-3b25-e8b055d54644@codeaurora.org \
--to=vivek.gautam@codeaurora.org \
--cc=architt@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sboyd@codeaurora.org \
--cc=sricharan@codeaurora.org \
--cc=tfiga@chromium.org \
--cc=will.deacon@arm.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
Powered by JetHome