From: Lucas Stach <l.stach@pengutronix.de>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Carlo Caione <ccaione@baylibre.com>,
linux-imx@nxp.com, kernel@pengutronix.de,
patchwork-lst@pengutronix.de
Subject: [PATCH 3/3] nvmem: imx-ocotp: broaden Kconfig dependency
Date: Mon, 11 Feb 2019 17:50:11 +0100 [thread overview]
Message-ID: <20190211165011.5114-3-l.stach@pengutronix.de> (raw)
In-Reply-To: <20190211165011.5114-1-l.stach@pengutronix.de>
The i.MX OCOTP controller is used in numerous Freescale/NXP
SoCs from the MXC family, so the strict dependency on the
i.MX6 SoC is too narrow. Broaden it to cover all the MXC
familiy members.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
drivers/nvmem/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
index 0a7a470ee859..665f2494095a 100644
--- a/drivers/nvmem/Kconfig
+++ b/drivers/nvmem/Kconfig
@@ -25,8 +25,8 @@ config NVMEM_IMX_IIM
will be called nvmem-imx-iim.
config NVMEM_IMX_OCOTP
- tristate "i.MX6 On-Chip OTP Controller support"
- depends on SOC_IMX6 || COMPILE_TEST
+ tristate "i.MX 6/7/8 On-Chip OTP Controller support"
+ depends on ARCH_MXC || COMPILE_TEST
depends on HAS_IOMEM
help
This is a driver for the On-Chip OTP Controller (OCOTP) available on
--
2.20.1
next prev parent reply other threads:[~2019-02-11 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 16:50 [PATCH 1/3] dt-bindings: imx-ocotp: Add i.MX8MQ compatible Lucas Stach
2019-02-11 16:50 ` [PATCH 2/3] nvmem: imx-ocotp: add support for imx8mq Lucas Stach
2019-02-11 16:50 ` Lucas Stach [this message]
2019-02-12 9:57 ` [PATCH 1/3] dt-bindings: imx-ocotp: Add i.MX8MQ compatible Abel Vesa
2019-02-25 23:34 ` Rob Herring
2019-02-26 9:04 ` Abel Vesa
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=20190211165011.5114-3-l.stach@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=ccaione@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-lst@pengutronix.de \
--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).