From: Daniel Lezcano <daniel.lezcano@linaro.org> To: sboyd@codeaurora.org, mturquette@baylibre.com Cc: lee.jones@linaro.org, xuwei5@hisilicon.com, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH V3 2/2] ARM64: dts: hi6220-hikey: Add clock binding for the pmic mfd Date: Mon, 17 Apr 2017 19:19:26 +0200 [thread overview] Message-ID: <1492449567-31399-2-git-send-email-daniel.lezcano@linaro.org> (raw) In-Reply-To: <1492449567-31399-1-git-send-email-daniel.lezcano@linaro.org> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org> --- Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt | 6 ++++++ arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 + 2 files changed, 7 insertions(+) diff --git a/Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt b/Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt index 0548569..9630ac0 100644 --- a/Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt +++ b/Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt @@ -16,6 +16,11 @@ Required properties: - reg: Base address of PMIC on Hi6220 SoC. - interrupt-controller: Hi655x has internal IRQs (has own IRQ domain). - pmic-gpios: The GPIO used by PMIC IRQ. +- #clock-cells: From common clock binding; shall be set to 0 + +Optional properties: +- clock-output-names: From common clock binding to override the + default output clock name Example: pmic: pmic@f8000000 { @@ -24,4 +29,5 @@ Example: interrupt-controller; #interrupt-cells = <2>; pmic-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>; + #clock-cells = <0>; } diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts index dba3c13..e0496f7 100644 --- a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts +++ b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts @@ -325,6 +325,7 @@ pmic: pmic@f8000000 { compatible = "hisilicon,hi655x-pmic"; reg = <0x0 0xf8000000 0x0 0x1000>; + #clock-cells = <0>; interrupt-controller; #interrupt-cells = <2>; pmic-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>; -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH V3 2/2] ARM64: dts: hi6220-hikey: Add clock binding for the pmic mfd Date: Mon, 17 Apr 2017 19:19:26 +0200 [thread overview] Message-ID: <1492449567-31399-2-git-send-email-daniel.lezcano@linaro.org> (raw) In-Reply-To: <1492449567-31399-1-git-send-email-daniel.lezcano@linaro.org> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org> --- Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt | 6 ++++++ arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 + 2 files changed, 7 insertions(+) diff --git a/Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt b/Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt index 0548569..9630ac0 100644 --- a/Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt +++ b/Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt @@ -16,6 +16,11 @@ Required properties: - reg: Base address of PMIC on Hi6220 SoC. - interrupt-controller: Hi655x has internal IRQs (has own IRQ domain). - pmic-gpios: The GPIO used by PMIC IRQ. +- #clock-cells: From common clock binding; shall be set to 0 + +Optional properties: +- clock-output-names: From common clock binding to override the + default output clock name Example: pmic: pmic at f8000000 { @@ -24,4 +29,5 @@ Example: interrupt-controller; #interrupt-cells = <2>; pmic-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>; + #clock-cells = <0>; } diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts index dba3c13..e0496f7 100644 --- a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts +++ b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts @@ -325,6 +325,7 @@ pmic: pmic at f8000000 { compatible = "hisilicon,hi655x-pmic"; reg = <0x0 0xf8000000 0x0 0x1000>; + #clock-cells = <0>; interrupt-controller; #interrupt-cells = <2>; pmic-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>; -- 1.9.1
next prev parent reply other threads:[~2017-04-17 17:20 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-17 17:19 [PATCH V3 1/2] clk: hi6220: Add the hi655x's pmic clock Daniel Lezcano 2017-04-17 17:19 ` Daniel Lezcano [this message] 2017-04-17 17:19 ` [PATCH V3 2/2] ARM64: dts: hi6220-hikey: Add clock binding for the pmic mfd Daniel Lezcano 2017-04-20 14:19 ` Rob Herring 2017-04-20 14:19 ` Rob Herring 2017-04-22 2:02 ` Stephen Boyd 2017-04-22 2:02 ` Stephen Boyd 2017-04-22 14:09 ` Daniel Lezcano 2017-04-22 14:09 ` Daniel Lezcano 2017-04-22 14:09 ` Daniel Lezcano 2017-04-24 8:59 ` Lee Jones 2017-04-24 8:59 ` Lee Jones 2017-04-24 9:16 ` Daniel Lezcano 2017-04-24 9:16 ` Daniel Lezcano 2017-04-24 13:01 ` Lee Jones 2017-04-24 13:01 ` Lee Jones 2017-04-24 13:01 ` Lee Jones 2017-04-24 20:11 ` Daniel Lezcano 2017-04-24 20:11 ` Daniel Lezcano 2017-04-24 20:19 ` Arnd Bergmann 2017-04-24 20:19 ` Arnd Bergmann 2017-04-24 20:19 ` Arnd Bergmann 2017-04-22 2:03 ` [PATCH V3 1/2] clk: hi6220: Add the hi655x's pmic clock Stephen Boyd
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=1492449567-31399-2-git-send-email-daniel.lezcano@linaro.org \ --to=daniel.lezcano@linaro.org \ --cc=devicetree@vger.kernel.org \ --cc=lee.jones@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mturquette@baylibre.com \ --cc=sboyd@codeaurora.org \ --cc=xuwei5@hisilicon.com \ /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: linkBe 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.