From: Rob Herring <robh@kernel.org>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
alexandre.torgue@st.com,
Etienne Carriere <etienne.carriere@st.com>,
srinivas.kandagatla@linaro.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org, fabrice.gasnier@st.com,
mcoquelin.stm32@gmail.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: nvmem: stm32: new property for data access
Date: Tue, 19 May 2020 13:00:19 -0600 [thread overview]
Message-ID: <20200519190019.GA478168@bogus> (raw)
In-Reply-To: <20200512131334.1750-1-etienne.carriere@linaro.org>
On Tue, 12 May 2020 15:13:34 +0200, Etienne Carriere wrote:
> From: Etienne Carriere <etienne.carriere@st.com>
>
> Introduce boolean property st,non-secure-otp for OTP data located
> in a factory programmed area that only secure firmware can access
> by default and that shall be reachable from the non-secure world.
>
> This change also allows additional properties for NVMEM nodes that
> were forbidden prior this change.
>
> Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
> ---
> Changes since v1:
> Change nvmem.yaml to allow additional properties in NVMEM nodes.
>
> Link to v1:
> https://lore.kernel.org/patchwork/patch/1239028/
>
> .../devicetree/bindings/nvmem/nvmem.yaml | 2 --
> .../bindings/nvmem/st,stm32-romem.yaml | 17 +++++++++++++++++
> 2 files changed, 17 insertions(+), 2 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2020-05-19 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 13:13 [PATCH v2] dt-bindings: nvmem: stm32: new property for data access Etienne Carriere
2020-05-19 19:00 ` Rob Herring [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=20200519190019.GA478168@bogus \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@linaro.org \
--cc=etienne.carriere@st.com \
--cc=fabrice.gasnier@st.com \
--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 \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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).