linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rnayak@codeaurora.org (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 08/11] arm: dts: qcom: Add #power-domain-cells property
Date: Mon, 27 Apr 2015 08:02:20 +0530	[thread overview]
Message-ID: <553D9FB4.6060107@codeaurora.org> (raw)
In-Reply-To: <CAPDyKFrUhx-_EHzR=j+tHUUDJPJb1Qw9d4eMV30_z2E-a9r=oA@mail.gmail.com>

On 04/24/2015 09:13 PM, Ulf Hansson wrote:
> On 24 April 2015 at 12:55, Rajendra Nayak <rnayak@codeaurora.org> wrote:
>> On 04/24/2015 03:15 PM, Ulf Hansson wrote:
>>>
>>> On 14 April 2015 at 15:12, Rajendra Nayak <rnayak@codeaurora.org> wrote:
>>>>
>>>> msm8974 has gcc and mmcc nodes, and apq8084 has a gcc node which
>>>> implement gdsc powerdomains. Add the #power-domain-cells property
>>>> to them.
>>>>
>>>> Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
>>>> ---
>>>>    arch/arm/boot/dts/qcom-apq8084.dtsi | 1 +
>>>>    arch/arm/boot/dts/qcom-msm8974.dtsi | 2 ++
>>>>    2 files changed, 3 insertions(+)
>>>>
>>>> diff --git a/arch/arm/boot/dts/qcom-apq8084.dtsi
>>>> b/arch/arm/boot/dts/qcom-apq8084.dtsi
>>>> index 1f130bc..55c281c 100644
>>>> --- a/arch/arm/boot/dts/qcom-apq8084.dtsi
>>>> +++ b/arch/arm/boot/dts/qcom-apq8084.dtsi
>>>> @@ -183,6 +183,7 @@
>>>>                           compatible = "qcom,gcc-apq8084";
>>>>                           #clock-cells = <1>;
>>>>                           #reset-cells = <1>;
>>>> +                       #power-domain-cells = <1>;
>>>
>>>
>>> So the PM domain will be apart of the clock-controller. That's a bit
>>> odd, but I guess the hardware is like that!?
>>
>>
>> Yes, the gdscs are all part of GCC controller.
>>
>>>
>>> Anyway, what I fail to understand from this patchset is who will be
>>> the actual consumer of the PM domain? In other words, what devices
>>> will hold the below property in its DT node?
>>>
>>> power_domains = <phandle index>;
>>>
>>> This is needed for genpd to have the device at probe time, attached to
>>> its PM domain.
>>
>>
>> Any device which belongs to the collapsible power domain (gdsc)
>> Examples are graphics, camera, video encode/decode block (venus) etc
>
> Then I expect those drivers to deploy runtime PM (if not already) and
> thus gdsc's PM domain will come into play.

Most of these drivers aren;t upstream yet. And one of the reasons I am
trying to get gdsc support upstream is so these drivers can then be
pushed upstream, with runtime support.

>
> But how will that relate to the GCC controller?
>
> For example when the gdsc's PM domain is about to be powered off,
> since all the devices within it has be runtime PM suspended. What
> happens with the GCC controller then?

I don;t seem to completely understand what you are asking. Are you
asking if the GCC controller itself is part of a collapsible power
domain?

>
> Kind regards
> Uffe
>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2015-04-27  2:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 13:12 [PATCH v5 00/11] Add support for QCOM GDSCs Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 01/11] clk: qcom: Add support for GDSCs Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 02/11] clk: qcom: gdsc: Prepare common clk probe to register gdscs Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 03/11] clk: qcom: gdsc: Add GDSCs in msm8916 GCC Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 04/11] clk: qcom: gdsc: Add GDSCs in msm8974 GCC Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 05/11] clk: qcom: gdsc: Add GDSCs in msm8974 MMCC Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 06/11] clk: qcom: gdsc: Add GDSCs in apq8084 GCC Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 07/11] clk: qcom: gdsc: Add GDSCs in apq8084 MMCC Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 08/11] arm: dts: qcom: Add #power-domain-cells property Rajendra Nayak
2015-04-24  9:45   ` Ulf Hansson
2015-04-24 10:55     ` Rajendra Nayak
2015-04-24 11:00       ` Rajendra Nayak
2015-04-24 15:43       ` Ulf Hansson
2015-04-27  2:32         ` Rajendra Nayak [this message]
2015-04-27  7:52           ` Ulf Hansson
2015-04-27  9:33             ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 09/11] clk: qcom: gdsc: Use PM clocks to control gdsc clocks Rajendra Nayak
2015-04-30 15:26   ` Stanimir Varbanov
2015-05-12  3:02     ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 10/11] clk: qcom: gdsc: Enable an RCG before turning on the gdsc Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 11/11] clk: qcom: gdsc: Add oxili GDSC for msm8916 Rajendra Nayak

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=553D9FB4.6060107@codeaurora.org \
    --to=rnayak@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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).