From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Fabrice Gasnier <fabrice.gasnier@st.com>,
robh+dt@kernel.org, alexandre.torgue@st.com
Cc: mark.rutland@arm.com, mcoquelin.stm32@gmail.com,
lionel.debieve@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 0/4] Add nvmem support on STM32
Date: Wed, 13 Feb 2019 10:34:19 +0000 [thread overview]
Message-ID: <46a59513-a322-1e14-41b5-ecbd4c478286@linaro.org> (raw)
In-Reply-To: <4aaa83b2-35a6-e2c2-a3f4-6579b5d67038@st.com>
On 13/02/2019 10:15, Fabrice Gasnier wrote:
> On 1/30/19 5:38 PM, Fabrice Gasnier wrote:
>> Non volatile memory area is available on STM32. It contains various
>> factory programmed information such as unique device ID, analog calibration...
>> This patchset adds NVMEM support to access these data.
>
> Hello,
>
> Gentle reminder for this new driver review
Nvmem provider driver itself looks fine for me, but I am unable to take
this as 5.1 material, as I normally take nvmem patches which are
reviewed and ready before rc5.
dt bindings patch needs an ack from DT maintainers.
Thanks,
srini
>
> Best Regards,
> Fabrice
>
>>
>> Fabrice Gasnier (4):
>> dt-bindings: nvmem: Add STM32 factory-programmed romem
>> nvmem: Add driver for STM32 factory-programmed read only mem
>> nvmem: stm32: add support for STM32MP15 BSEC to control OTP data
>> ARM: dts: stm32: Add romem and temperature calibration on stm32mp157c
>>
>> .../devicetree/bindings/nvmem/st,stm32-romem.txt | 31 ++++
>> arch/arm/boot/dts/stm32mp157c.dtsi | 13 ++
>> drivers/nvmem/Kconfig | 10 +
>> drivers/nvmem/Makefile | 2 +
>> drivers/nvmem/stm32-romem.c | 202 +++++++++++++++++++++
>> 5 files changed, 258 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/nvmem/st,stm32-romem.txt
>> create mode 100644 drivers/nvmem/stm32-romem.c
>>
next prev parent reply other threads:[~2019-02-13 10:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 16:38 [PATCH 0/4] Add nvmem support on STM32 Fabrice Gasnier
2019-01-30 16:38 ` [PATCH 1/4] dt-bindings: nvmem: Add STM32 factory-programmed romem Fabrice Gasnier
2019-02-18 13:20 ` Fabrice Gasnier
2019-02-25 16:53 ` Rob Herring
2019-02-26 9:14 ` Fabrice Gasnier
2019-02-26 17:58 ` Rob Herring
2019-01-30 16:38 ` [PATCH 2/4] nvmem: Add driver for STM32 factory-programmed read only mem Fabrice Gasnier
2019-01-30 16:38 ` [PATCH 3/4] nvmem: stm32: add support for STM32MP15 BSEC to control OTP data Fabrice Gasnier
2019-01-30 16:38 ` [PATCH 4/4] ARM: dts: stm32: Add romem and temperature calibration on stm32mp157c Fabrice Gasnier
2019-02-13 10:15 ` [PATCH 0/4] Add nvmem support on STM32 Fabrice Gasnier
2019-02-13 10:34 ` Srinivas Kandagatla [this message]
2019-02-14 10:36 ` Fabrice Gasnier
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=46a59513-a322-1e14-41b5-ecbd4c478286@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--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=lionel.debieve@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.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).