From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Kumar Gala <galak@codeaurora.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 2/2] irqchip: gic: Document optional Clock and Power Domain properties
Date: Tue, 15 Sep 2015 13:57:01 -0500 [thread overview]
Message-ID: <55F869FD.4090900@kernel.org> (raw)
In-Reply-To: <1442261204-30931-3-git-send-email-geert+renesas@glider.be>
On 09/14/2015 03:06 PM, Geert Uytterhoeven wrote:
> Depending on the GIC variant, the GIC module has one or more clock
> inputs. Document the optional "clocks" and "clock-names" properties,
> and their possible values, based on the Technical Reference Manuals.
> optional.
>
> Add the optional "power-domains" property.
>
> This will allow to describe in DT the relationship between the GIC and
> the Clock and/or Power Domain topology on SoCs where this is relevant
> and needed for proper operation.
>
> Note: As the current GIC driver doesn't support Runtime PM yet, PM
> Domain constraints must be handled elsewhere in e.g. platform code.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Note: v1 was Acked-by: Rob Herring <robh@kernel.org>, but I didn't add
> it, due to the addition of clock-names.
For both: ack.
>
> v2:
> - Add "clock-names",
> - Document clock inputs on various GIC variants.
>
> Clock inputs are based on the following documentation:
> - "ARM11 MPCore Processor Technical Reference Manual" (r2p0),
> - "Cortex-A9 MPCore Technical Reference Manual" (r4p1, r2p0),
> - "Cortex-A15 Technical Reference Manual" (r4p0, r2p0),
> - "CoreLink GIC-400 Generic Interrupt Controller Technical Reference
> Manual" (r0p1, r0p0),
> - "PrimeCell Generic Interrupt Controller (PL390) Technical Reference
> Manual" (r0p0).
>
> I could not find clock input information in:
> - "ARM1176JZF Development Chip Technical Reference Manual" (r0p0),
> - "Cortex-A7 MPCore processors" (r0p5, r0p3).
>
> Other:
> - "brcm,brahma-b15-gic" seems to be always used together with
> "arm,cortex-a15-gic".
>
> No access to datasheets:
> - "qcom,msm-8660-qgic",
> - "qcom,msm-qgic2".
> ---
> Documentation/devicetree/bindings/arm/gic.txt | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/gic.txt b/Documentation/devicetree/bindings/arm/gic.txt
> index 24742853ba460223..cc56021eb60babea 100644
> --- a/Documentation/devicetree/bindings/arm/gic.txt
> +++ b/Documentation/devicetree/bindings/arm/gic.txt
> @@ -59,6 +59,21 @@ Optional
> regions, used when the GIC doesn't have banked registers. The offset is
> cpu-offset * cpu-nr.
>
> +- clocks : List of phandle and clock-specific pairs, one for each entry
> + in clock-names.
> +- clock-names : List of names for the GIC clock input(s). Valid clock names
> + depend on the GIC variant:
> + "ic_clk" (for "arm,arm11mp-gic")
> + "PERIPHCLKEN" (for "arm,cortex-a15-gic")
> + "PERIPHCLK", "PERIPHCLKEN" (for "arm,cortex-a9-gic")
> + "clk" (for "arm,gic-400")
> + "gclk" (for "arm,pl390")
> +
> +- power-domains : A phandle and PM domain specifier as defined by bindings of
> + the power controller specified by phandle, used when the GIC
> + is part of a Power or Clock Domain.
> +
> +
> Example:
>
> intc: interrupt-controller@fff11000 {
>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] irqchip: gic: Document optional Clock and Power Domain properties
Date: Tue, 15 Sep 2015 18:57:01 +0000 [thread overview]
Message-ID: <55F869FD.4090900@kernel.org> (raw)
In-Reply-To: <1442261204-30931-3-git-send-email-geert+renesas@glider.be>
On 09/14/2015 03:06 PM, Geert Uytterhoeven wrote:
> Depending on the GIC variant, the GIC module has one or more clock
> inputs. Document the optional "clocks" and "clock-names" properties,
> and their possible values, based on the Technical Reference Manuals.
> optional.
>
> Add the optional "power-domains" property.
>
> This will allow to describe in DT the relationship between the GIC and
> the Clock and/or Power Domain topology on SoCs where this is relevant
> and needed for proper operation.
>
> Note: As the current GIC driver doesn't support Runtime PM yet, PM
> Domain constraints must be handled elsewhere in e.g. platform code.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Note: v1 was Acked-by: Rob Herring <robh@kernel.org>, but I didn't add
> it, due to the addition of clock-names.
For both: ack.
>
> v2:
> - Add "clock-names",
> - Document clock inputs on various GIC variants.
>
> Clock inputs are based on the following documentation:
> - "ARM11 MPCore Processor Technical Reference Manual" (r2p0),
> - "Cortex-A9 MPCore Technical Reference Manual" (r4p1, r2p0),
> - "Cortex-A15 Technical Reference Manual" (r4p0, r2p0),
> - "CoreLink GIC-400 Generic Interrupt Controller Technical Reference
> Manual" (r0p1, r0p0),
> - "PrimeCell Generic Interrupt Controller (PL390) Technical Reference
> Manual" (r0p0).
>
> I could not find clock input information in:
> - "ARM1176JZF Development Chip Technical Reference Manual" (r0p0),
> - "Cortex-A7 MPCore processors" (r0p5, r0p3).
>
> Other:
> - "brcm,brahma-b15-gic" seems to be always used together with
> "arm,cortex-a15-gic".
>
> No access to datasheets:
> - "qcom,msm-8660-qgic",
> - "qcom,msm-qgic2".
> ---
> Documentation/devicetree/bindings/arm/gic.txt | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/gic.txt b/Documentation/devicetree/bindings/arm/gic.txt
> index 24742853ba460223..cc56021eb60babea 100644
> --- a/Documentation/devicetree/bindings/arm/gic.txt
> +++ b/Documentation/devicetree/bindings/arm/gic.txt
> @@ -59,6 +59,21 @@ Optional
> regions, used when the GIC doesn't have banked registers. The offset is
> cpu-offset * cpu-nr.
>
> +- clocks : List of phandle and clock-specific pairs, one for each entry
> + in clock-names.
> +- clock-names : List of names for the GIC clock input(s). Valid clock names
> + depend on the GIC variant:
> + "ic_clk" (for "arm,arm11mp-gic")
> + "PERIPHCLKEN" (for "arm,cortex-a15-gic")
> + "PERIPHCLK", "PERIPHCLKEN" (for "arm,cortex-a9-gic")
> + "clk" (for "arm,gic-400")
> + "gclk" (for "arm,pl390")
> +
> +- power-domains : A phandle and PM domain specifier as defined by bindings of
> + the power controller specified by phandle, used when the GIC
> + is part of a Power or Clock Domain.
> +
> +
> Example:
>
> intc: interrupt-controller@fff11000 {
>
WARNING: multiple messages have this Message-ID (diff)
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] irqchip: gic: Document optional Clock and Power Domain properties
Date: Tue, 15 Sep 2015 13:57:01 -0500 [thread overview]
Message-ID: <55F869FD.4090900@kernel.org> (raw)
In-Reply-To: <1442261204-30931-3-git-send-email-geert+renesas@glider.be>
On 09/14/2015 03:06 PM, Geert Uytterhoeven wrote:
> Depending on the GIC variant, the GIC module has one or more clock
> inputs. Document the optional "clocks" and "clock-names" properties,
> and their possible values, based on the Technical Reference Manuals.
> optional.
>
> Add the optional "power-domains" property.
>
> This will allow to describe in DT the relationship between the GIC and
> the Clock and/or Power Domain topology on SoCs where this is relevant
> and needed for proper operation.
>
> Note: As the current GIC driver doesn't support Runtime PM yet, PM
> Domain constraints must be handled elsewhere in e.g. platform code.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Note: v1 was Acked-by: Rob Herring <robh@kernel.org>, but I didn't add
> it, due to the addition of clock-names.
For both: ack.
>
> v2:
> - Add "clock-names",
> - Document clock inputs on various GIC variants.
>
> Clock inputs are based on the following documentation:
> - "ARM11 MPCore Processor Technical Reference Manual" (r2p0),
> - "Cortex-A9 MPCore Technical Reference Manual" (r4p1, r2p0),
> - "Cortex-A15 Technical Reference Manual" (r4p0, r2p0),
> - "CoreLink GIC-400 Generic Interrupt Controller Technical Reference
> Manual" (r0p1, r0p0),
> - "PrimeCell Generic Interrupt Controller (PL390) Technical Reference
> Manual" (r0p0).
>
> I could not find clock input information in:
> - "ARM1176JZF Development Chip Technical Reference Manual" (r0p0),
> - "Cortex-A7 MPCore processors" (r0p5, r0p3).
>
> Other:
> - "brcm,brahma-b15-gic" seems to be always used together with
> "arm,cortex-a15-gic".
>
> No access to datasheets:
> - "qcom,msm-8660-qgic",
> - "qcom,msm-qgic2".
> ---
> Documentation/devicetree/bindings/arm/gic.txt | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/gic.txt b/Documentation/devicetree/bindings/arm/gic.txt
> index 24742853ba460223..cc56021eb60babea 100644
> --- a/Documentation/devicetree/bindings/arm/gic.txt
> +++ b/Documentation/devicetree/bindings/arm/gic.txt
> @@ -59,6 +59,21 @@ Optional
> regions, used when the GIC doesn't have banked registers. The offset is
> cpu-offset * cpu-nr.
>
> +- clocks : List of phandle and clock-specific pairs, one for each entry
> + in clock-names.
> +- clock-names : List of names for the GIC clock input(s). Valid clock names
> + depend on the GIC variant:
> + "ic_clk" (for "arm,arm11mp-gic")
> + "PERIPHCLKEN" (for "arm,cortex-a15-gic")
> + "PERIPHCLK", "PERIPHCLKEN" (for "arm,cortex-a9-gic")
> + "clk" (for "arm,gic-400")
> + "gclk" (for "arm,pl390")
> +
> +- power-domains : A phandle and PM domain specifier as defined by bindings of
> + the power controller specified by phandle, used when the GIC
> + is part of a Power or Clock Domain.
> +
> +
> Example:
>
> intc: interrupt-controller at fff11000 {
>
next prev parent reply other threads:[~2015-09-15 18:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 20:06 [PATCH v2 0/2] ARM: gic: Document optional Clock and Power Domain properties Geert Uytterhoeven
2015-09-14 20:06 ` Geert Uytterhoeven
2015-09-14 20:06 ` Geert Uytterhoeven
2015-09-14 20:06 ` [PATCH v2 1/2] irqchip: gic: Add arm,pl390 support Geert Uytterhoeven
2015-09-14 20:06 ` Geert Uytterhoeven
2015-09-14 20:06 ` Geert Uytterhoeven
2015-09-22 10:54 ` [tip:irq/core] irqchip/gic: " tip-bot for Geert Uytterhoeven
2015-09-14 20:06 ` [PATCH v2 2/2] irqchip: gic: Document optional Clock and Power Domain properties Geert Uytterhoeven
2015-09-14 20:06 ` Geert Uytterhoeven
2015-09-14 20:06 ` Geert Uytterhoeven
2015-09-15 18:57 ` Rob Herring [this message]
2015-09-15 18:57 ` Rob Herring
2015-09-15 18:57 ` Rob Herring
2015-09-22 10:54 ` [tip:irq/core] irqchip/gic: " tip-bot for Geert Uytterhoeven
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=55F869FD.4090900@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert+renesas@glider.be \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.