Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: dongas86@gmail.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/2] ARM: dts: imx7s: add snvs rtc clock
Date: Tue, 9 Jan 2018 17:47:16 +0800	[thread overview]
Message-ID: <20180109094716.GH26312@b29396-OptiPlex-7040> (raw)
In-Reply-To: <1515489651-13488-2-git-send-email-Anson.Huang@nxp.com>

On Tue, Jan 09, 2018 at 05:20:51PM +0800, Anson Huang wrote:
> Add i.MX7 SNVS RTC clock.
> 
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> ---
> changes since v2:
> 	improve the binding doc statement about clocks.
>  Documentation/devicetree/bindings/crypto/fsl-sec4.txt | 15 +++++++++++++++
>  arch/arm/boot/dts/imx7s.dtsi                          |  2 ++
>  2 files changed, 17 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
> index 76aec8a..7329f29 100644
> --- a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
> +++ b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
> @@ -415,12 +415,25 @@ Secure Non-Volatile Storage (SNVS) Low Power (LP) RTC Node
>  	value type: <u32>
>  	Definition: LP register offset. default it is 0x34.
>  
> +   - clocks
> +      Usage: required if SNVS LP RTC requires explicit enablement of clocks
> +      Value type: <prop_encoded-array>
> +      Definition:  a clock specifier describing the clock required for
> +          enabling and disabling SNVS LP RTC.
> +

This clock seem optional.
Should we indicate it here explicitly?

BTW, i thought we probably could update poweroff and key as well at
the same time since device tree changes can go separately.
Does it make sense?

Regards
Dong Aisheng

> +   - clock-names
> +      Usage: required if SNVS LP RTC requires explicit enablement of clocks
> +      Value type: <string>
> +      Definition: clock name string should be "snvs-rtc".
> +
>  EXAMPLE
>  	sec_mon_rtc_lp at 1 {
>  		compatible = "fsl,sec-v4.0-mon-rtc-lp";
>  		interrupts = <93 2>;
>  		regmap = <&snvs>;
>  		offset = <0x34>;
> +		clocks = <&clks IMX7D_SNVS_CLK>;
> +		clock-names = "snvs-rtc";
>  	};
>  
>  =====================================================================
> @@ -543,6 +556,8 @@ FULL EXAMPLE
>  			regmap = <&sec_mon>;
>  			offset = <0x34>;
>  			interrupts = <93 2>;
> +			clocks = <&clks IMX7D_SNVS_CLK>;
> +			clock-names = "snvs-rtc";
>  		};
>  
>  		snvs-pwrkey at 020cc000 {
> diff --git a/arch/arm/boot/dts/imx7s.dtsi b/arch/arm/boot/dts/imx7s.dtsi
> index 9aa2bb9..02baf42 100644
> --- a/arch/arm/boot/dts/imx7s.dtsi
> +++ b/arch/arm/boot/dts/imx7s.dtsi
> @@ -551,6 +551,8 @@
>  					offset = <0x34>;
>  					interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>,
>  						     <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>;
> +					clocks = <&clks IMX7D_SNVS_CLK>;
> +					clock-names = "snvs-rtc";
>  				};
>  
>  				snvs_poweroff: snvs-poweroff {
> -- 
> 1.9.1
> 

  reply	other threads:[~2018-01-09  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09  9:20 [PATCH V3 1/2] clk: imx: imx7d: add the snvs clock Anson Huang
2018-01-09  9:20 ` [PATCH V3 2/2] ARM: dts: imx7s: add snvs rtc clock Anson Huang
2018-01-09  9:47   ` Dong Aisheng [this message]
2018-01-09 10:03     ` Anson Huang
2018-01-09  9:43 ` [PATCH V3 1/2] clk: imx: imx7d: add the snvs clock Dong Aisheng
2018-01-09 10:10   ` Anson Huang

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=20180109094716.GH26312@b29396-OptiPlex-7040 \
    --to=dongas86@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox