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 1/3] dt-bindings: imx-ocotp: Add i.MX8MQ compatible
Date: Mon, 11 Feb 2019 17:50:09 +0100 [thread overview]
Message-ID: <20190211165011.5114-1-l.stach@pengutronix.de> (raw)
Add compatible for i.MX8MQ and add both i.MX7D/S and i.M8MQ
to the description.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
Documentation/devicetree/bindings/nvmem/imx-ocotp.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/nvmem/imx-ocotp.txt b/Documentation/devicetree/bindings/nvmem/imx-ocotp.txt
index 792bc5fafeb9..bb8fb8fc6217 100644
--- a/Documentation/devicetree/bindings/nvmem/imx-ocotp.txt
+++ b/Documentation/devicetree/bindings/nvmem/imx-ocotp.txt
@@ -1,7 +1,8 @@
Freescale i.MX6 On-Chip OTP Controller (OCOTP) device tree bindings
This binding represents the on-chip eFuse OTP controller found on
-i.MX6Q/D, i.MX6DL/S, i.MX6SL, i.MX6SX, i.MX6UL and i.MX6SLL SoCs.
+i.MX6Q/D, i.MX6DL/S, i.MX6SL, i.MX6SX, i.MX6UL, i.MX6SLL, i.MX7D/S
+and i.MX8MQ SoCs.
Required properties:
- compatible: should be one of
@@ -11,6 +12,7 @@ Required properties:
"fsl,imx6ul-ocotp" (i.MX6UL),
"fsl,imx7d-ocotp" (i.MX7D/S),
"fsl,imx6sll-ocotp" (i.MX6SLL),
+ "fsl,imx8mq-ocotp" (i.MX8MQ),
followed by "syscon".
- #address-cells : Should be 1
- #size-cells : Should be 1
--
2.20.1
next 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 Lucas Stach [this message]
2019-02-11 16:50 ` [PATCH 2/3] nvmem: imx-ocotp: add support for imx8mq Lucas Stach
2019-02-11 16:50 ` [PATCH 3/3] nvmem: imx-ocotp: broaden Kconfig dependency Lucas Stach
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-1-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).