From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Anson Huang <Anson.Huang@nxp.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bai Ping <ping.bai@nxp.com>,
Stefan Wahren <stefan.wahren@i2se.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 0/3] nvmem: imx: correct nregs for i.MX6UL/ULL/SLL
Date: Sun, 08 Oct 2023 16:10:19 +0800 [thread overview]
Message-ID: <20231008-nvmem-imx-v1-0-cabeb18ab676@nxp.com> (raw)
The current code does not include the register space hole, after check
the fuse map of the three SoCs, update the nregs to fix the issue.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
Peng Fan (3):
nvmem: imx: correct nregs for i.MX6SLL
nvmem: imx: correct nregs for i.MX6UL
nvmem: imx: correct nregs for i.MX6ULL
drivers/nvmem/imx-ocotp.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
---
base-commit: 0f0fe5040de5e5fd9b040672e37725b046e312f0
change-id: 20231008-nvmem-imx-1af696badaf5
Best regards,
--
Peng Fan <peng.fan@nxp.com>
next reply other threads:[~2023-10-08 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 8:10 Peng Fan (OSS) [this message]
2023-10-08 8:10 ` [PATCH 1/3] nvmem: imx: correct nregs for i.MX6SLL Peng Fan (OSS)
2023-10-08 13:07 ` Greg Kroah-Hartman
2023-10-08 8:10 ` [PATCH 2/3] nvmem: imx: correct nregs for i.MX6UL Peng Fan (OSS)
2023-10-08 13:07 ` Greg Kroah-Hartman
2023-10-08 8:10 ` [PATCH 3/3] nvmem: imx: correct nregs for i.MX6ULL Peng Fan (OSS)
2023-10-08 13:08 ` Greg Kroah-Hartman
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=20231008-nvmem-imx-v1-0-cabeb18ab676@nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=ping.bai@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stefan.wahren@i2se.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®