From: Rob Herring <robh@kernel.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Christophe Roullier <christophe.roullier@st.com>,
kernel@pengutronix.de, Arnaud Pouliquen <arnaud.pouliquen@st.com>,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: stm32: add simple-mfd compatible for tamp node
Date: Mon, 26 Oct 2020 09:36:56 -0500 [thread overview]
Message-ID: <20201026143656.GA118160@bogus> (raw)
In-Reply-To: <20201021102855.18026-1-a.fatoum@pengutronix.de>
On Wed, Oct 21, 2020 at 12:28:55PM +0200, Ahmad Fatoum wrote:
> The stm32mp1 TAMP (Tamper and backup registers) does tamper detection
> and features 32 backup registers that, being in the RTC domain, may
> survive even with Vdd switched off.
>
> This makes it suitable for use to communicate a reboot mode from OS
> to bootloader via the syscon-reboot-mode binding. Add a "simple-mfd"
> to support probing such a child node. The actual reboot mode
> node could then be defined in a board.dts or fixed up by the bootloader.
'simple-mfd' implies there is no dependency on the parent node for the
child (such as the regmap perhaps). Is that the case here?
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> v1 available here:
> https://lore.kernel.org/linux-arm-kernel/20200916142216.25142-1-a.fatoum@pengutronix.de/
>
> v1 -> v2:
> - new patch, rebased on top of
> https://lore.kernel.org/r/20201014125441.2457-1-arnaud.pouliquen@st.com
> ---
> .../devicetree/bindings/arm/stm32/st,stm32-syscon.yaml | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml b/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml
> index 6634b3e0853e..4684017a42e4 100644
> --- a/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml
> +++ b/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml
> @@ -19,8 +19,11 @@ properties:
> - st,stm32mp151-pwr-mcu
> - st,stm32-syscfg
> - st,stm32-power-config
> - - st,stm32-tamp
> - const: syscon
> + - items:
> + - const: st,stm32-tamp
> + - const: syscon
> + - const: simple-mfd
>
> reg:
> maxItems: 1
> --
> 2.28.0
>
next prev parent reply other threads:[~2020-10-26 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 10:28 [PATCH v2 1/2] dt-bindings: arm: stm32: add simple-mfd compatible for tamp node Ahmad Fatoum
2020-10-21 10:28 ` [PATCH v2 2/2] ARM: dts: stm32: support child mfd cells for the stm32mp1 TAMP syscon Ahmad Fatoum
2020-11-17 11:18 ` Alexandre Torgue
2020-10-26 14:36 ` Rob Herring [this message]
2020-10-26 21:30 ` [PATCH v2 1/2] dt-bindings: arm: stm32: add simple-mfd compatible for tamp node Ahmad Fatoum
2020-10-27 12:15 ` Rob Herring
2020-11-10 10:27 ` Ahmad Fatoum
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=20201026143656.GA118160@bogus \
--to=robh@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=alexandre.torgue@st.com \
--cc=arnaud.pouliquen@st.com \
--cc=christophe.roullier@st.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
/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).