From mboxrd@z Thu Jan 1 00:00:00 1970 From: Will Deacon Subject: Re: [PATCH V3 0/5] iommu/arm-smmu: Add runtime pm/sleep support Date: Fri, 31 Mar 2017 18:54:57 +0100 Message-ID: <20170331175457.GD4897@arm.com> References: <1489073748-3659-1-git-send-email-sricharan@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1489073748-3659-1-git-send-email-sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Sricharan R Cc: robin.murphy-5wv7dgnIgG8@public.gmane.org, joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org, iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org, linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, mathieu.poirier-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, mark.rutland-5wv7dgnIgG8@public.gmane.org List-Id: linux-arm-msm@vger.kernel.org On Thu, Mar 09, 2017 at 09:05:43PM +0530, Sricharan R 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 symmu's > runtime to follow the master's runtime pm, so the smmu remains > powered only when the masters use it. Do you have any numbers for the power savings you achieve with this? How often do we actually manage to stop the SMMU clocks on an SoC with a handful of masters? In other words, is this too coarse-grained to be useful, or is it common that all the devices upstream of the SMMU are suspended? Thanks, Will > > Took some reference from the exynos runtime patches [2]. > Tested this with MDP, GPU, VENUS devices on apq8096-db820c board. > > Previous version of the patchset [1]. > > [V3] > * Reworked the patches to keep the clocks init/enabling function > seperately for each compatible. > > * Added clocks bindings for MMU40x/500. > > * Added a new compatible for qcom,smmu-v2 implementation and > the clock bindings for the same. > > * Rebased on top of 4.11-rc1 > > [V2] > * Split the patches little differently. > > * Addressed comments. > > * Removed the patch #4 [3] from previous post > for arm-smmu context save restore. Planning to > post this separately after reworking/addressing Robin's > feedback. > > * Reversed the sequence to disable clocks than enabling. > This was required for those cases where the > clocks are populated in a dependent order from DT. > > [1] https://www.spinics.net/lists/linux-arm-msm/msg23870.html > [2] https://lkml.org/lkml/2016/10/20/70 > [3] https://patchwork.kernel.org/patch/9389717/ > > Sricharan R (5): > iommu/arm-smmu: Add pm_runtime/sleep ops > iommu/arm-smmu: Add support for MMU40x/500 clocks > drivers: arm-smmu: Add clock support for QCOM_SMMUV2 > iommu/arm-smmu: Invoke pm_runtime during probe, add/remove device > iommu/arm-smmu: Add the device_link between masters and smmu > > .../devicetree/bindings/iommu/arm,smmu.txt | 35 +++ > drivers/iommu/arm-smmu.c | 349 ++++++++++++++++++++- > 2 files changed, 373 insertions(+), 11 deletions(-) > > -- > QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from foss.arm.com ([217.140.101.70]:34782 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933419AbdCaRym (ORCPT ); Fri, 31 Mar 2017 13:54:42 -0400 Date: Fri, 31 Mar 2017 18:54:57 +0100 From: Will Deacon To: Sricharan R Cc: robin.murphy@arm.com, joro@8bytes.org, iommu@lists.linux-foundation.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, m.szyprowski@samsung.com, linux-clk@vger.kernel.org, sboyd@codeaurora.org, devicetree@vger.kernel.org, robh+dt@kernel.org, mathieu.poirier@linaro.org, mark.rutland@arm.com Subject: Re: [PATCH V3 0/5] iommu/arm-smmu: Add runtime pm/sleep support Message-ID: <20170331175457.GD4897@arm.com> References: <1489073748-3659-1-git-send-email-sricharan@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1489073748-3659-1-git-send-email-sricharan@codeaurora.org> Sender: linux-clk-owner@vger.kernel.org List-ID: On Thu, Mar 09, 2017 at 09:05:43PM +0530, Sricharan R 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 symmu's > runtime to follow the master's runtime pm, so the smmu remains > powered only when the masters use it. Do you have any numbers for the power savings you achieve with this? How often do we actually manage to stop the SMMU clocks on an SoC with a handful of masters? In other words, is this too coarse-grained to be useful, or is it common that all the devices upstream of the SMMU are suspended? Thanks, Will > > Took some reference from the exynos runtime patches [2]. > Tested this with MDP, GPU, VENUS devices on apq8096-db820c board. > > Previous version of the patchset [1]. > > [V3] > * Reworked the patches to keep the clocks init/enabling function > seperately for each compatible. > > * Added clocks bindings for MMU40x/500. > > * Added a new compatible for qcom,smmu-v2 implementation and > the clock bindings for the same. > > * Rebased on top of 4.11-rc1 > > [V2] > * Split the patches little differently. > > * Addressed comments. > > * Removed the patch #4 [3] from previous post > for arm-smmu context save restore. Planning to > post this separately after reworking/addressing Robin's > feedback. > > * Reversed the sequence to disable clocks than enabling. > This was required for those cases where the > clocks are populated in a dependent order from DT. > > [1] https://www.spinics.net/lists/linux-arm-msm/msg23870.html > [2] https://lkml.org/lkml/2016/10/20/70 > [3] https://patchwork.kernel.org/patch/9389717/ > > Sricharan R (5): > iommu/arm-smmu: Add pm_runtime/sleep ops > iommu/arm-smmu: Add support for MMU40x/500 clocks > drivers: arm-smmu: Add clock support for QCOM_SMMUV2 > iommu/arm-smmu: Invoke pm_runtime during probe, add/remove device > iommu/arm-smmu: Add the device_link between masters and smmu > > .../devicetree/bindings/iommu/arm,smmu.txt | 35 +++ > drivers/iommu/arm-smmu.c | 349 ++++++++++++++++++++- > 2 files changed, 373 insertions(+), 11 deletions(-) > > -- > QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation > From mboxrd@z Thu Jan 1 00:00:00 1970 From: will.deacon@arm.com (Will Deacon) Date: Fri, 31 Mar 2017 18:54:57 +0100 Subject: [PATCH V3 0/5] iommu/arm-smmu: Add runtime pm/sleep support In-Reply-To: <1489073748-3659-1-git-send-email-sricharan@codeaurora.org> References: <1489073748-3659-1-git-send-email-sricharan@codeaurora.org> Message-ID: <20170331175457.GD4897@arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Mar 09, 2017 at 09:05:43PM +0530, Sricharan R 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 symmu's > runtime to follow the master's runtime pm, so the smmu remains > powered only when the masters use it. Do you have any numbers for the power savings you achieve with this? How often do we actually manage to stop the SMMU clocks on an SoC with a handful of masters? In other words, is this too coarse-grained to be useful, or is it common that all the devices upstream of the SMMU are suspended? Thanks, Will > > Took some reference from the exynos runtime patches [2]. > Tested this with MDP, GPU, VENUS devices on apq8096-db820c board. > > Previous version of the patchset [1]. > > [V3] > * Reworked the patches to keep the clocks init/enabling function > seperately for each compatible. > > * Added clocks bindings for MMU40x/500. > > * Added a new compatible for qcom,smmu-v2 implementation and > the clock bindings for the same. > > * Rebased on top of 4.11-rc1 > > [V2] > * Split the patches little differently. > > * Addressed comments. > > * Removed the patch #4 [3] from previous post > for arm-smmu context save restore. Planning to > post this separately after reworking/addressing Robin's > feedback. > > * Reversed the sequence to disable clocks than enabling. > This was required for those cases where the > clocks are populated in a dependent order from DT. > > [1] https://www.spinics.net/lists/linux-arm-msm/msg23870.html > [2] https://lkml.org/lkml/2016/10/20/70 > [3] https://patchwork.kernel.org/patch/9389717/ > > Sricharan R (5): > iommu/arm-smmu: Add pm_runtime/sleep ops > iommu/arm-smmu: Add support for MMU40x/500 clocks > drivers: arm-smmu: Add clock support for QCOM_SMMUV2 > iommu/arm-smmu: Invoke pm_runtime during probe, add/remove device > iommu/arm-smmu: Add the device_link between masters and smmu > > .../devicetree/bindings/iommu/arm,smmu.txt | 35 +++ > drivers/iommu/arm-smmu.c | 349 ++++++++++++++++++++- > 2 files changed, 373 insertions(+), 11 deletions(-) > > -- > QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation >