From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: srinivas.kandagatla@linaro.org, shawnguo@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, aisheng.dong@nxp.com,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 1/2] nvmem: kconfig: set i.MX OCOTP default y
Date: Mon, 3 Jun 2024 15:00:06 +0800 [thread overview]
Message-ID: <20240603070007.2413599-1-peng.fan@oss.nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
If ARCH_MXC is selected, set NVMEM_IMX_OCOTP[*] default y which will make
nfs rootfs work since i.MX network driver needs read mac address from
fuse.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
drivers/nvmem/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
index 283134498fbc..7e92e855eb50 100644
--- a/drivers/nvmem/Kconfig
+++ b/drivers/nvmem/Kconfig
@@ -76,6 +76,7 @@ config NVMEM_IMX_OCOTP
tristate "i.MX 6/7/8 On-Chip OTP Controller support"
depends on ARCH_MXC || COMPILE_TEST
depends on HAS_IOMEM
+ default y if ARCH_MXC
help
This is a driver for the On-Chip OTP Controller (OCOTP) available on
i.MX6 SoCs, providing access to 4 Kbits of one-time programmable
@@ -89,6 +90,7 @@ config NVMEM_IMX_OCOTP_ELE
depends on ARCH_MXC || COMPILE_TEST
depends on HAS_IOMEM
depends on OF
+ default y if ARCH_MXC
help
This is a driver for the On-Chip OTP Controller (OCOTP)
available on i.MX SoCs which has ELE.
@@ -97,6 +99,7 @@ config NVMEM_IMX_OCOTP_SCU
tristate "i.MX8 SCU On-Chip OTP Controller support"
depends on IMX_SCU
depends on HAVE_ARM_SMCCC
+ default y if ARCH_MXC
help
This is a driver for the SCU On-Chip OTP Controller (OCOTP)
available on i.MX8 SoCs.
--
2.37.1
next reply other threads:[~2024-06-03 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 7:00 Peng Fan (OSS) [this message]
2024-06-03 7:00 ` [PATCH 2/2] arm64: defconfig: remove IMX OCOTP Peng Fan (OSS)
2024-06-22 10:47 ` [PATCH 1/2] nvmem: kconfig: set i.MX OCOTP default y Srinivas Kandagatla
2024-06-24 0:06 ` Peng Fan
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=20240603070007.2413599-1-peng.fan@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=shawnguo@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
all inboxes | Powered by JetHome®