LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Amelie Delaunay <amelie.delaunay@st.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Rob Herring <robh+dt@kernel.org>,
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 v3 0/4] Introduce STM32MP1 RTC
Date: Tue, 22 May 2018 20:11:26 +0200 [thread overview]
Message-ID: <20180522181126.GL13267@piout.net> (raw)
In-Reply-To: <1526558666-24243-1-git-send-email-amelie.delaunay@st.com>
On 17/05/2018 14:04:22+0200, Amelie Delaunay wrote:
> This series introduces STM32MP1 RTC.
> On STM32MP1:
> - two clocks are needed, plck and rtc_ck;
> - to wakeup the system, a wakeup alarm interrupt is needed;
> - some registers or bits have moved, but the operation is the same;
> - the Backup Domain Protection (DBP) is not managed by RTC driver.
>
> ---
> Changes in v3:
> * Move cleanup changes in a separate patch
> * Replace regs and evts by pointers to ensure no copy is made
> * Set all registers offset as u16 instead of u8 and u16
> * Fix Kbuild smatch warning:
> drivers/rtc/rtc-stm32.c:827 stm32_rtc_probe()
> warn: always true condition '(regs.verr != ~0) => (0-u16max != (-1))'
>
> Changes in v2:
> * One compatible per line in bindings file
> * Remove unnecessary comment under rtc_ck as this clock is required for all
> * Remove interrupts-extended and add stm32mp1 rtc alarm wakeup interrupt in
> interrupts property description
>
> Amelie Delaunay (4):
> rtc: stm32: fix misspelling and misalignment issues
> rtc: stm32: rework register management to prepare other version of RTC
> dt-bindings: rtc: update stm32-rtc documentation for stm32mp1 rtc
> rtc: stm32: add stm32mp1 rtc support
>
> .../devicetree/bindings/rtc/st,stm32-rtc.txt | 27 +-
> drivers/rtc/rtc-stm32.c | 273 ++++++++++++++++-----
> 2 files changed, 229 insertions(+), 71 deletions(-)
>
Applied, thanks.
--
Alexandre Belloni, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-05-22 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 12:04 Amelie Delaunay
2018-05-17 12:04 ` [PATCH v3 1/4] rtc: stm32: fix misspelling and misalignment issues Amelie Delaunay
2018-05-17 12:04 ` [PATCH v3 2/4] rtc: stm32: rework register management to prepare other version of RTC Amelie Delaunay
2018-05-17 12:04 ` [PATCH v3 3/4] dt-bindings: rtc: update stm32-rtc documentation for stm32mp1 rtc Amelie Delaunay
2018-05-22 17:17 ` Rob Herring
2018-05-17 12:04 ` [PATCH v3 4/4] rtc: stm32: add stm32mp1 rtc support Amelie Delaunay
2018-05-22 18:11 ` Alexandre Belloni [this message]
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=20180522181126.GL13267@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--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 \
--cc=robh+dt@kernel.org \
--subject='Re: [PATCH v3 0/4] Introduce 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).