LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Amelie Delaunay <amelie.delaunay@st.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: rtc: update stm32-rtc documentation for stm32mp1 rtc
Date: Thu, 26 Apr 2018 22:01:40 -0500 [thread overview]
Message-ID: <20180427030140.nmlqmpewqatabnmt@rob-hp-laptop> (raw)
In-Reply-To: <1524144845-23016-3-git-send-email-amelie.delaunay@st.com>
On Thu, Apr 19, 2018 at 03:34:04PM +0200, Amelie Delaunay wrote:
> RTC embedded in stm32mp1 SoC is slightly different from stm32h7 one, it
> doesn't require to disable backup domain write protection, and rtc_ck
> parent clock assignment isn't allowed.
> To sum up, stm32mp1 RTC requires 2 clocks, pclk and rtc_ck, and an RTC
> alarm interrupt.
>
> Signed-off-by: Amelie Delaunay <amelie.delaunay@st.com>
> ---
> .../devicetree/bindings/rtc/st,stm32-rtc.txt | 27 +++++++++++++++++-----
> 1 file changed, 21 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/rtc/st,stm32-rtc.txt b/Documentation/devicetree/bindings/rtc/st,stm32-rtc.txt
> index 00f8b5d..f1c2080 100644
> --- a/Documentation/devicetree/bindings/rtc/st,stm32-rtc.txt
> +++ b/Documentation/devicetree/bindings/rtc/st,stm32-rtc.txt
> @@ -1,25 +1,31 @@
> STM32 Real Time Clock
>
> Required properties:
> -- compatible: can be either "st,stm32-rtc" or "st,stm32h7-rtc", depending on
> - the device is compatible with stm32(f4/f7) or stm32h7.
> +- compatible: can be "st,stm32-rtc", "st,stm32h7-rtc" or "st,stm32mp1-rtc",
> + depending on the device is compatible with stm32(f4/f7), stm32h7
> + or stm32mp1.
One compatible per line please.
> - reg: address range of rtc register set.
> - clocks: can use up to two clocks, depending on part used:
> - "rtc_ck": RTC clock source.
> - It is required on stm32(f4/f7) and stm32h7.
> + It is required on stm32(f4/f7/h7/mp1).
IOW, required for all?
> - "pclk": RTC APB interface clock.
> It is not present on stm32(f4/f7).
> - It is required on stm32h7.
> + It is required on stm32(h7/mp1).
> - clock-names: must be "rtc_ck" and "pclk".
> - It is required only on stm32h7.
> + It is required on stm32(h7/mp1).
> - interrupt-parent: phandle for the interrupt controller.
> + It is required on stm32(f4/f7/h7).
> - interrupts: rtc alarm interrupt.
> +- interrupts-extended: replace interrupts property on stm32mp1, to specify rtc
> + alarm wakeup interrupt, which is on exti interrupt controller instead of gic.
> + It is required on stm32mp1.
Just document 'interrupts'. interrupts-extended is implicitly supported
and what the interrupts are connected to is outside the scope of this
binding.
> - st,syscfg: phandle/offset/mask triplet. The phandle to pwrcfg used to
> access control register at offset, and change the dbp (Disable Backup
> Protection) bit represented by the mask, mandatory to disable/enable backup
> domain (RTC registers) write protection.
> + It is required on stm32(f4/f7/h7).
>
> -Optional properties (to override default rtc_ck parent clock):
> +Optional properties (to override default rtc_ck parent clock on stm32(f4/f7/h7):
> - assigned-clocks: reference to the rtc_ck clock entry.
> - assigned-clock-parents: phandle of the new parent clock of rtc_ck.
>
> @@ -48,3 +54,12 @@ Example:
> interrupt-names = "alarm";
> st,syscfg = <&pwrcfg 0x00 0x100>;
> };
> +
> + rtc: rtc@5c004000 {
> + compatible = "st,stm32mp1-rtc";
> + reg = <0x5c004000 0x400>;
> + clocks = <&rcc RTCAPB>, <&rcc RTC>;
> + clock-names = "pclk", "rtc_ck";
> + interrupts-extended = <&intc GIC_SPI 3 IRQ_TYPE_NONE>,
> + <&exti 19 1>;
> + };
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-04-27 3:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 13:34 [PATCH 0/3] Introduce STM32MP1 RTC Amelie Delaunay
2018-04-19 13:34 ` [PATCH 1/3] rtc: stm32: rework register management to prepare other version of RTC Amelie Delaunay
2018-04-19 13:34 ` [PATCH 2/3] dt-bindings: rtc: update stm32-rtc documentation for stm32mp1 rtc Amelie Delaunay
2018-04-27 3:01 ` Rob Herring [this message]
2018-05-09 7:25 ` Amelie DELAUNAY
2018-04-19 13:34 ` [PATCH 3/3] rtc: stm32: add stm32mp1 rtc support Amelie Delaunay
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=20180427030140.nmlqmpewqatabnmt@rob-hp-laptop \
--to=robh@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--subject='Re: [PATCH 2/3] dt-bindings: rtc: update stm32-rtc documentation for stm32mp1 rtc' \
/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
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).