mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Patrick Delaunay <patrick.delaunay@foss.st.com>,
	Russell King <linux@armlinux.org.uk>
Cc: "Alexander Stein" <alexander.stein@ew.tq-group.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Eugen Hristev" <eugen.hristev@collabora.com>,
	"Fabio Estevam" <festevam@gmail.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Mark Brown" <broonie@kernel.org>,
	"Michael Walle" <michael@walle.cc>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"William Zhang" <william.zhang@broadcom.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: multi_v7_defconfig: enable NVMEM driver for STM32
Date: Thu, 2 Feb 2023 13:35:55 +0100	[thread overview]
Message-ID: <244541fb-993e-3c50-d671-0730811335ae@foss.st.com> (raw)
In-Reply-To: <20230130135951.1.I609229f603520144b3831bea4b026000ae0dd9a8@changeid>

On 1/30/23 14:00, Patrick Delaunay wrote:
> Enable the STMicroelectronics NVMEM drivers used on
> STM32 MPU, STM32MP15x and STM32MP13x, to access OTPs.
> 
> Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
> ---
> 
>   arch/arm/configs/multi_v7_defconfig | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
> index d2f218341ad0..9b3ef21f44c1 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -1209,6 +1209,7 @@ CONFIG_RAS=y
>   CONFIG_NVMEM_IMX_OCOTP=y
>   CONFIG_NVMEM_QCOM_QFPROM=y
>   CONFIG_NVMEM_ROCKCHIP_EFUSE=m
> +CONFIG_NVMEM_STM32_ROMEM=m
>   CONFIG_NVMEM_SUNXI_SID=y
>   CONFIG_NVMEM_VF610_OCOTP=y
>   CONFIG_NVMEM_MESON_MX_EFUSE=m

Applied on stm32-next.

Thanks.
Alex

      reply	other threads:[~2023-02-02 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 13:00 Patrick Delaunay
2023-02-02 12:35 ` Alexandre TORGUE [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=244541fb-993e-3c50-d671-0730811335ae@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=eugen.hristev@collabora.com \
    --cc=f.fainelli@gmail.com \
    --cc=festevam@gmail.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael@walle.cc \
    --cc=patrick.delaunay@foss.st.com \
    --cc=rafal@milecki.pl \
    --cc=william.zhang@broadcom.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
all inboxes | Powered by JetHome®