From: Raju P L S S S N <rplsssn@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: ilina@codearuroa.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RFC v2 2/4] dt-bindings: introduce System PM domain bindings for Qualcomm SoCs
Date: Wed, 24 Oct 2018 01:05:15 +0530 [thread overview]
Message-ID: <ddcf0993-4d8e-91d7-cd83-4133034384ba@codeaurora.org> (raw)
In-Reply-To: <20181017184247.GA28562@bogus>
On 10/18/2018 12:12 AM, Rob Herring wrote:
> On Wed, Oct 10, 2018 at 09:24:37PM +0530, Raju P.L.S.S.S.N wrote:
>> Add device binding documentation for Qualcomm Technology Inc's System PM
>> domain driver. The driver is used for managing system sleep activities
>> that are required when application processor is going to deepest low
>> power mode.
>>
>> Cc: devicetree@vger.kernel.org
>> Signed-off-by: Raju P.L.S.S.S.N <rplsssn@codeaurora.org>
>> ---
>> .../bindings/soc/qcom/system_pm_domain.txt | 38 ++++++++++++++++++++++
>> 1 file changed, 38 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/soc/qcom/system_pm_domain.txt
>>
>> diff --git a/Documentation/devicetree/bindings/soc/qcom/system_pm_domain.txt b/Documentation/devicetree/bindings/soc/qcom/system_pm_domain.txt
>> new file mode 100644
>> index 0000000..9f913c3
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/soc/qcom/system_pm_domain.txt
>> @@ -0,0 +1,38 @@
>> +Qualcomm Technologies system power domain
>> +-----------------------------------------
>> +
>> +System pm domain handles the tasks that need to be performed during application
>> +processor deeper low power mode entry for QCOM SoCs which have hardened IP blocks
>> +combinedly called as RPMH (Resource Power Manager Hardened) for shared resource
>> +management. Flushing the buffered requests to TCS (Triggered Command Set) in RSC
>> +(Resource State Coordinator) and programming the wakeup timer in PDC (Power
>> +Domain Controller) for timer based wakeup are handled as part of domain power
>> +down.
>> +
>> +The bindings for System PM domain is specified in the RSC section in devicetree.
>> +
>> +Properties:
>> +- compatible:
>> + Usage: required
>> + Value type: <string>
>> + Definition: must be "qcom,system-pm-domain".
>> +
>> +- #power-domain-cells: number of cells in power domain specifier;
>> + must be 0.
>> +
>> +Node of a device using power domains must have a power-domains property
>> +defined with a phandle to respective power domain.
>> +
>> +Example:
>> +
>> + apps_rsc: rsc@179c0000 {
>> + [...]
>> + system_pd: system-power-domain {
>> + compatible = "qcom,system-pm";
>> + #power-domain-cells = <0>;
>
> I don't understand why this is split from "qcom,cpu-pm-domain". Just
> make the parent (RSC) a power domain provider with multiple domains. As
> long as each domain doesn't have its own resources, you don't need child
> nodes here.
Hi Rob,
Since the patch had cc:devicetree, it was unintentionally posted in
mailing list. Sorry about that and please ignore this one. The intended
version is posted as https://lkml.org/lkml/2018/10/11/28
The power down activities are handled by top level rpmh layer[1] which
are not core functions of RSC driver. Though it is doable, it would be
messy to invoke calls to top level rpmh layer by declaring RSC parent
node itself as power domain provider.
[1].https://patchwork.kernel.org/patch/10474327/
Thanks,
Raju
>
> Rob
>
prev parent reply other threads:[~2018-10-23 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1539186879-10009-1-git-send-email-rplsssn@codeaurora.org>
2018-10-10 15:54 ` [PATCH RFC v2 2/4] dt-bindings: introduce System PM domain bindings for Qualcomm SoCs Raju P.L.S.S.S.N
2018-10-17 18:42 ` Rob Herring
2018-10-23 19:35 ` Raju P L S S S N [this message]
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=ddcf0993-4d8e-91d7-cd83-4133034384ba@codeaurora.org \
--to=rplsssn@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=ilina@codearuroa.org \
--cc=robh@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).