From: Benjamin Gaignard <benjamin.gaignard@st.com>
To: <lee.jones@linaro.org>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <mcoquelin.stm32@gmail.com>,
<alexandre.torgue@st.com>, <daniel.lezcano@linaro.org>,
<tglx@linutronix.de>, <fabrice.gasnier@st.com>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: [PATCH v4 0/3] clockevent: add low power STM32 timer
Date: Mon, 17 Feb 2020 14:45:43 +0100 [thread overview]
Message-ID: <20200217134546.14562-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.
version 4:
- move defines in mfd/stm32-lptimer.h
- change compatible and subnode names
- document wakeup-source property
- reword commit message
- make driver Kconfig depends of MFD_STM32_LPTIMER
- remove useless include
- remove rate and clk fields from the private structure
- to add comments about the registers sequence in stm32_clkevent_lp_set_timer
- rework probe function and use devm_request_irq()
- do not allow module to be removed
version 3:
- fix timer set sequence
- don't forget to free irq on remove function
- use devm_kzalloc to simplify errors handling in probe function
version 2:
- stm32 clkevent driver is now a child of the stm32 lp timer node
- add a probe function and adpat the driver to use regmap provide
by it parent
- stop using timer_of helpers
Benjamin Gaignard (3):
dt-bindings: mfd: Document STM32 low power timer bindings
mfd: stm32: Add defines to be used for clkevent purpose
clocksource: Add Low Power STM32 timers driver
.../devicetree/bindings/mfd/st,stm32-lptimer.yaml | 16 ++
drivers/clocksource/Kconfig | 7 +
drivers/clocksource/Makefile | 1 +
drivers/clocksource/timer-stm32-lp.c | 213 +++++++++++++++++++++
include/linux/mfd/stm32-lptimer.h | 5 +
5 files changed, 242 insertions(+)
create mode 100644 drivers/clocksource/timer-stm32-lp.c
--
2.15.0
next reply other threads:[~2020-02-17 13:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 13:45 Benjamin Gaignard [this message]
2020-02-17 13:45 ` [PATCH v4 1/3] dt-bindings: mfd: Document STM32 low power timer bindings Benjamin Gaignard
2020-02-18 21:24 ` Rob Herring
2020-02-17 13:45 ` [PATCH v4 2/3] mfd: stm32: Add defines to be used for clkevent purpose Benjamin Gaignard
2020-02-20 9:38 ` Daniel Lezcano
2020-02-20 13:37 ` Lee Jones
2020-03-19 10:10 ` Lee Jones
2020-03-19 10:28 ` Benjamin GAIGNARD
2020-03-19 10:35 ` Daniel Lezcano
2020-02-17 13:45 ` [PATCH v4 3/3] clocksource: Add Low Power STM32 timers driver Benjamin Gaignard
2020-02-20 10:36 ` Daniel Lezcano
2020-02-20 10:45 ` Benjamin GAIGNARD
2020-02-20 11:05 ` Daniel Lezcano
2020-03-13 13:34 ` Daniel Lezcano
2020-03-13 13:45 ` 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=20200217134546.14562-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=fabrice.gasnier@st.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.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).