From: Patrick Delaunay <patrick.delaunay@foss.st.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Patrick Delaunay <patrick.delaunay@foss.st.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: [PATCH v2 0/3] nvmem: stm32: several minor improvements
Date: Mon, 17 Oct 2022 17:49:54 +0200 [thread overview]
Message-ID: <20221017154957.277120-1-patrick.delaunay@foss.st.com> (raw)
Several minor improvement for BSEC driver = nvmem stm32 romem
- move STM32MP15_BSEC_NUM_LOWER in config, to prepare introduction
of next STM32MP products with more OTP
- add warning when upper OTPs are updated to indicate possible ECC issue
for second update
- add nvmem type attribute so userspace is able to know how the data is
stored in OTPs
Changes in v2:
- Add patch "move STM32MP15_BSEC_NUM_LOWER in config" in the serie,
solve dependency issue for "priv->lower" in patch "nvmem: stm32:
add warning when upper OTPs are updated"
Patrick Delaunay (3):
nvmem: stm32: move STM32MP15_BSEC_NUM_LOWER in config
nvmem: stm32: add warning when upper OTPs are updated
nvmem: stm32: add nvmem type attribute
drivers/nvmem/stm32-romem.c | 25 ++++++++++++++++++++-----
1 file changed, 20 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2022-10-17 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 15:49 Patrick Delaunay [this message]
2022-10-17 15:49 ` [PATCH v2 1/3] nvmem: stm32: move STM32MP15_BSEC_NUM_LOWER in config Patrick Delaunay
2022-10-17 15:49 ` [PATCH v2 2/3] nvmem: stm32: add warning when upper OTPs are updated Patrick Delaunay
2022-10-17 15:49 ` [PATCH v2 3/3] nvmem: stm32: add nvmem type attribute Patrick Delaunay
2022-10-31 17:41 ` [PATCH v2 0/3] nvmem: stm32: several minor improvements Srinivas Kandagatla
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=20221017154957.277120-1-patrick.delaunay@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.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=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).