From: Benjamin Gaignard <benjamin.gaignard@st.com>
To: <daniel.lezcano@linaro.org>, <tglx@linutronix.de>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<mcoquelin.stm32@gmail.com>, <alexandre.torgue@st.com>,
<linux@armlinux.org.uk>, <p.paillet@st.com>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: [PATCH 0/3] clockevent: add low power STM32 timer
Date: Thu, 9 Jan 2020 15:53:30 +0100 [thread overview]
Message-ID: <20200109145333.12260-1-benjamin.gaignard@st.com> (raw)
This series add low power timer as boadcast clockevent device.
Low power timer could runs even when CPUs are in idle mode and
could wakeup them.
Benjamin Gaignard (3):
dt-bindings: timer: Add STM32 Low Power Timer bindings
clocksource: Add Low Power STM32 timers driver
ARM: stm32: select STM32 low power timer clock event driver
.../bindings/timer/st,stm32-lp-timer.yaml | 44 +++++
arch/arm/mach-stm32/Kconfig | 1 +
drivers/clocksource/Kconfig | 5 +
drivers/clocksource/Makefile | 1 +
drivers/clocksource/timer-stm32-lp.c | 186 +++++++++++++++++++++
5 files changed, 237 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/st,stm32-lp-timer.yaml
create mode 100644 drivers/clocksource/timer-stm32-lp.c
--
2.15.0
next reply other threads:[~2020-01-09 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 14:53 Benjamin Gaignard [this message]
2020-01-09 14:53 ` [PATCH 1/3] dt-bindings: timer: Add STM32 Low Power Timer bindings Benjamin Gaignard
2020-01-15 14:35 ` Rob Herring
2020-01-15 14:45 ` Benjamin Gaignard
2020-01-15 19:00 ` Rob Herring
2020-01-15 19:17 ` Benjamin Gaignard
2020-01-09 14:53 ` [PATCH 2/3] clocksource: Add Low Power STM32 timers driver Benjamin Gaignard
2020-01-16 9:06 ` Linus Walleij
2020-01-16 15:44 ` Benjamin Gaignard
2020-01-16 15:53 ` Linus Walleij
2020-01-09 14:53 ` [PATCH 3/3] ARM: stm32: select STM32 low power timer clock event driver Benjamin Gaignard
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=20200109145333.12260-1-benjamin.gaignard@st.com \
--to=benjamin.gaignard@st.com \
--cc=alexandre.torgue@st.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.paillet@st.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).