mbox series

[v2,0/6] Add RSC power domain support

Message ID 20190823081703.17325-1-mkshah@codeaurora.org (mailing list archive)
Headers show
Series Add RSC power domain support | expand

Message

Maulik Shah Aug. 23, 2019, 8:16 a.m. UTC
Changes in v2:
- Add Stephen's Reviewed-By to the first three patches
- Addressed Stephen's comments on fourth patch
- Include changes to connect rpmh domain to cpuidle and genpds

Resource State Coordinator (RSC) is responsible for powering off/lowering
the requirements from CPU subsystem for the associated hardware like buses,
clocks, and regulators when all CPUs and cluster is powered down.

RSC power domain uses last-man activities provided by genpd framework based on
Ulf Hansoon's patch series[1], when the cluster of CPUs enter deepest idle
states. As a part of domain poweroff, RSC can lower resource state requirements
by flushing the cached sleep and wake state votes for resources.

Dependencies:

[1] https://lkml.org/lkml/2019/5/13/839

Maulik Shah (6):
  drivers: qcom: rpmh: fix macro to accept NULL argument
  drivers: qcom: rpmh: remove rpmh_flush export
  dt-bindings: soc: qcom: Add RSC power domain specifier
  drivers: qcom: rpmh-rsc: Add RSC power domain support
  arm64: dts: Convert to the hierarchical CPU topology layout for sdm845
  arm64: dts: Add rsc power domain for sdm845

 .../devicetree/bindings/soc/qcom/rpmh-rsc.txt |   8 ++
 arch/arm64/boot/dts/qcom/sdm845.dtsi          | 105 +++++++++++++-----
 drivers/soc/qcom/rpmh-internal.h              |   3 +
 drivers/soc/qcom/rpmh-rsc.c                   |  84 ++++++++++++++
 drivers/soc/qcom/rpmh.c                       |  22 ++--
 include/soc/qcom/rpmh.h                       |   5 -
 6 files changed, 185 insertions(+), 42 deletions(-)

Comments

Matthias Kaehlcke Jan. 21, 2020, 7:05 p.m. UTC | #1
Hi Maulik,

What is the status of this series? It seems it hasn't been updated since
you sent it in August last year. Do you plan to send a v3 in the near future
to address the outstanding comments?

Thanks

Matthias

On Fri, Aug 23, 2019 at 01:46:57PM +0530, Maulik Shah wrote:
> Changes in v2:
> - Add Stephen's Reviewed-By to the first three patches
> - Addressed Stephen's comments on fourth patch
> - Include changes to connect rpmh domain to cpuidle and genpds
> 
> Resource State Coordinator (RSC) is responsible for powering off/lowering
> the requirements from CPU subsystem for the associated hardware like buses,
> clocks, and regulators when all CPUs and cluster is powered down.
> 
> RSC power domain uses last-man activities provided by genpd framework based on
> Ulf Hansoon's patch series[1], when the cluster of CPUs enter deepest idle
> states. As a part of domain poweroff, RSC can lower resource state requirements
> by flushing the cached sleep and wake state votes for resources.
> 
> Dependencies:
> 
> [1] https://lkml.org/lkml/2019/5/13/839
> 
> Maulik Shah (6):
>   drivers: qcom: rpmh: fix macro to accept NULL argument
>   drivers: qcom: rpmh: remove rpmh_flush export
>   dt-bindings: soc: qcom: Add RSC power domain specifier
>   drivers: qcom: rpmh-rsc: Add RSC power domain support
>   arm64: dts: Convert to the hierarchical CPU topology layout for sdm845
>   arm64: dts: Add rsc power domain for sdm845
> 
>  .../devicetree/bindings/soc/qcom/rpmh-rsc.txt |   8 ++
>  arch/arm64/boot/dts/qcom/sdm845.dtsi          | 105 +++++++++++++-----
>  drivers/soc/qcom/rpmh-internal.h              |   3 +
>  drivers/soc/qcom/rpmh-rsc.c                   |  84 ++++++++++++++
>  drivers/soc/qcom/rpmh.c                       |  22 ++--
>  include/soc/qcom/rpmh.h                       |   5 -
>  6 files changed, 185 insertions(+), 42 deletions(-)
> 
> -- 
> QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation.
>
Maulik Shah Jan. 25, 2020, 3:36 p.m. UTC | #2
Hi Matthias,

Yes i will soon post a v3 series addressing outstanding comments.

Thanks,

Maulik

On 1/22/2020 12:35 AM, Matthias Kaehlcke wrote:
> Hi Maulik,
>
> What is the status of this series? It seems it hasn't been updated since
> you sent it in August last year. Do you plan to send a v3 in the near future
> to address the outstanding comments?