From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: dts: vf610: Add SNVS node
Date: Sun, 28 Sep 2014 12:02:34 +0800 [thread overview]
Message-ID: <20140928040233.GG12999@dragon> (raw)
In-Reply-To: <49cb7f5fc8319fc47dc2919a2ccbff981196d4ff.1411736171.git.maitysanchayan@gmail.com>
On Fri, Sep 26, 2014 at 06:44:00PM +0530, Sanchayan Maity wrote:
> This adds a devicetree node for RTC support
> for the VF610 platform.
>
> Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
> ---
> arch/arm/boot/dts/vf610.dtsi | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/arch/arm/boot/dts/vf610.dtsi b/arch/arm/boot/dts/vf610.dtsi
> index 4d2ec32..3c0c757 100644
> --- a/arch/arm/boot/dts/vf610.dtsi
> +++ b/arch/arm/boot/dts/vf610.dtsi
> @@ -381,6 +381,21 @@
> <&clks VF610_CLK_DMAMUX3>;
> };
>
> + snvs0: snvs at 400a7000 {
> + compatible = "fsl,sec-v4.0-mon", "simple-bus";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0 0x400a7000 0x2000>;
> +
> + snvs-rtc-lp at 34 {
> + compatible = "fsl,sec-v4.0-mon-rtc-lp";
> + reg = <0x34 0x58>;
> + interrupts = <0 100 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clks VF610_CLK_SNVS>;
> + clock-names = "snvs";
The name should describe the clock usage inside the block, so "snvs" is
not a good description.
Shawn
> + };
> + };
> +
> uart4: serial at 400a9000 {
> compatible = "fsl,vf610-lpuart";
> reg = <0x400a9000 0x1000>;
> --
> 1.7.9.5
>
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawn.guo@freescale.com>
To: Sanchayan Maity <maitysanchayan@gmail.com>
Cc: <kernel@pengutronix.de>, <a.zummo@towertech.it>,
<b35083@freescale.com>, <rtc-linux@googlegroups.com>,
<stefan@agner.ch>, <linux@arm.linux.org.uk>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] ARM: dts: vf610: Add SNVS node
Date: Sun, 28 Sep 2014 12:02:34 +0800 [thread overview]
Message-ID: <20140928040233.GG12999@dragon> (raw)
In-Reply-To: <49cb7f5fc8319fc47dc2919a2ccbff981196d4ff.1411736171.git.maitysanchayan@gmail.com>
On Fri, Sep 26, 2014 at 06:44:00PM +0530, Sanchayan Maity wrote:
> This adds a devicetree node for RTC support
> for the VF610 platform.
>
> Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
> ---
> arch/arm/boot/dts/vf610.dtsi | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/arch/arm/boot/dts/vf610.dtsi b/arch/arm/boot/dts/vf610.dtsi
> index 4d2ec32..3c0c757 100644
> --- a/arch/arm/boot/dts/vf610.dtsi
> +++ b/arch/arm/boot/dts/vf610.dtsi
> @@ -381,6 +381,21 @@
> <&clks VF610_CLK_DMAMUX3>;
> };
>
> + snvs0: snvs@400a7000 {
> + compatible = "fsl,sec-v4.0-mon", "simple-bus";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0 0x400a7000 0x2000>;
> +
> + snvs-rtc-lp@34 {
> + compatible = "fsl,sec-v4.0-mon-rtc-lp";
> + reg = <0x34 0x58>;
> + interrupts = <0 100 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clks VF610_CLK_SNVS>;
> + clock-names = "snvs";
The name should describe the clock usage inside the block, so "snvs" is
not a good description.
Shawn
> + };
> + };
> +
> uart4: serial@400a9000 {
> compatible = "fsl,vf610-lpuart";
> reg = <0x400a9000 0x1000>;
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2014-09-28 4:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 13:13 [PATCH 0/3] Add SNVS clock gating and clock support to rtc-snvs driver Sanchayan Maity
2014-09-26 13:13 ` Sanchayan Maity
2014-09-26 13:13 ` [PATCH 1/3] ARM: imx: clk-vf610: Add SNVS clock Sanchayan Maity
2014-09-26 13:13 ` Sanchayan Maity
2014-09-26 13:14 ` [PATCH 2/3] ARM: dts: vf610: Add SNVS node Sanchayan Maity
2014-09-26 13:14 ` Sanchayan Maity
2014-09-28 4:02 ` Shawn Guo [this message]
2014-09-28 4:02 ` Shawn Guo
2014-09-26 13:14 ` [PATCH 3/3] drivers/rtc/rtc-snvs: Add clock support Sanchayan Maity
2014-09-26 13:14 ` Sanchayan Maity
2014-09-28 3:56 ` Shawn Guo
2014-09-28 3:56 ` Shawn Guo
2014-09-29 12:57 ` Stefan Agner
2014-09-29 12:57 ` Stefan Agner
2014-09-29 13:05 ` Stefan Agner
2014-09-29 13:05 ` Stefan Agner
2014-09-30 4:57 ` Sanchayan Maity
2014-09-30 4:57 ` Sanchayan Maity
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=20140928040233.GG12999@dragon \
--to=shawn.guo@freescale.com \
--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 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.