From: Valentin Caron <valentin.caron@foss.st.com>
To: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Gabriel Fernandez <gabriel.fernandez@foss.st.com>,
Amelie Delaunay <amelie.delaunay@foss.st.com>,
Valentin Caron <valentin.caron@foss.st.com>,
<linux-rtc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/6] rtc: stm32: add alarm out and LSCO features.
Date: Wed, 4 May 2022 15:02:27 +0200 [thread overview]
Message-ID: <20220504130233.330983-1-valentin.caron@foss.st.com> (raw)
On STM32MP1x SOCs, RTC is able to output some signals on its own pins.
This series add the possibility to select two of these signals on
RTC pins :
- LSCO (Low Speed Clock Output) that allow to output LSE clock on a pin.
On STM32MP1x Discovery boards this feature is used to generate a clock
to Wifi/Bluetooth module.
- Alarm out that allow to send a pulse on a pin when alarm A of the RTC
expires.
Amelie Delaunay (2):
dt-bindings: rtc: stm32: add st,lsco optional property to select
output
rtc: stm32: add Low Speed Clock Output (LSCO) support
Gabriel Fernandez (2):
ARM: dts: stm32: add RTC LSCO support on stm32mp157c-dk2
ARM: dts: stm32: add RTC LSCO support on stm32mp135f-dk
Valentin Caron (2):
dt-bindings: rtc: stm32: add alarm A out property to select output
rtc: stm32: add alarm A out feature
.../devicetree/bindings/rtc/st,stm32-rtc.yaml | 37 +++
arch/arm/boot/dts/stm32mp13-pinctrl.dtsi | 6 +
arch/arm/boot/dts/stm32mp135f-dk.dts | 4 +
arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 6 +
arch/arm/boot/dts/stm32mp157c-dk2.dts | 7 +
drivers/rtc/Kconfig | 1 +
drivers/rtc/rtc-stm32.c | 210 ++++++++++++++++++
include/dt-bindings/rtc/rtc-stm32.h | 14 ++
8 files changed, 285 insertions(+)
create mode 100644 include/dt-bindings/rtc/rtc-stm32.h
--
2.25.1
next reply other threads:[~2022-05-04 13:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 13:02 Valentin Caron [this message]
2022-05-04 13:02 ` [PATCH 1/6] dt-bindings: rtc: stm32: add st,lsco optional property to select output Valentin Caron
2022-05-16 23:52 ` Rob Herring
2022-05-04 13:06 ` [PATCH 2/6] dt-bindings: rtc: stm32: add alarm A out " Valentin Caron
2022-05-04 15:42 ` Rob Herring
2022-05-04 20:27 ` Alexandre Belloni
2022-05-23 12:34 ` Valentin CARON
2022-06-24 8:35 ` Valentin CARON
2022-07-22 16:02 ` Alexandre Belloni
2022-05-04 13:06 ` [PATCH 3/6] rtc: stm32: add Low Speed Clock Output (LSCO) support Valentin Caron
2022-05-04 13:06 ` [PATCH 4/6] rtc: stm32: add alarm A out feature Valentin Caron
2022-05-04 13:06 ` [PATCH 5/6] ARM: dts: stm32: add RTC LSCO support on stm32mp157c-dk2 Valentin Caron
2022-05-04 13:06 ` [PATCH 6/6] ARM: dts: stm32: add RTC LSCO support on stm32mp135f-dk Valentin Caron
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=20220504130233.330983-1-valentin.caron@foss.st.com \
--to=valentin.caron@foss.st.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@foss.st.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).