From: Conor Dooley <conor@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Frank.Li@nxp.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: imx-iim: Allow syscon fallback on i.MX5
Date: Sun, 18 Oct 2026 20:05:16 +0100 [thread overview]
Message-ID: <20261018-suspend-uphill-7fab7a4dd8b2@spud> (raw)
In-Reply-To: <20261016232800.536654-1-festevam@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2350 bytes --]
On Fri, Oct 16, 2026 at 08:27:59PM -0300, Fabio Estevam wrote:
> The i.MX51 and i.MX53 SoC device code reads the unique ID through
> syscon_regmap_lookup_by_compatible(). Their IIM nodes therefore need the
> syscon fallback so the syscon core can instantiate a regmap.
>
> Allow the two-item compatible sequence for these SoCs. This prepares for
> restoring the fallback removed while making the IIM nodes conform to the
> binding.
Making it a syscon is only the right thing to do if it genuinely is a
syscon. If it's not, then don't. The nvmem driver doesn't treat this as
a syscon, so the inbuilt regmap locking doesn't actually do anything
here.
Surely the right thing to do is for the soc driver to access the efuse
through the nvmem subsystem somehow?
>
> Cc: stable@vger.kernel.org
> Fixes: d5b55c35e033 ("ARM: dts: imx: Fix the iim compatible string")
A binding should not have a fixes tag pointing to a devicetree.
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
> .../devicetree/bindings/nvmem/imx-iim.yaml | 20 +++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/imx-iim.yaml b/Documentation/devicetree/bindings/nvmem/imx-iim.yaml
> index bb37d72c9eaa..ebfd947e6800 100644
> --- a/Documentation/devicetree/bindings/nvmem/imx-iim.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/imx-iim.yaml
> @@ -20,13 +20,17 @@ allOf:
>
> properties:
> compatible:
> - enum:
> - - fsl,imx25-iim
> - - fsl,imx27-iim
> - - fsl,imx31-iim
> - - fsl,imx35-iim
> - - fsl,imx51-iim
> - - fsl,imx53-iim
> + oneOf:
> + - enum:
> + - fsl,imx25-iim
> + - fsl,imx27-iim
> + - fsl,imx31-iim
> + - fsl,imx35-iim
> + - items:
> + - enum:
> + - fsl,imx51-iim
> + - fsl,imx53-iim
> + - const: syscon
>
> reg:
> maxItems: 1
> @@ -50,7 +54,7 @@ examples:
> #include <dt-bindings/clock/imx5-clock.h>
>
> iim: efuse@63f98000 {
> - compatible = "fsl,imx53-iim";
> + compatible = "fsl,imx53-iim", "syscon";
> reg = <0x63f98000 0x4000>;
> interrupts = <69>;
> clocks = <&clks IMX5_CLK_IIM_GATE>;
> --
> 2.43.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-10-18 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 23:27 [PATCH 1/2] dt-bindings: nvmem: imx-iim: Allow syscon fallback on i.MX5 Fabio Estevam
2026-10-16 23:28 ` [PATCH 2/2] ARM: dts: imx5: Restore IIM syscon fallback Fabio Estevam
2026-10-18 19:05 ` Conor Dooley [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=20261018-suspend-uphill-7fab7a4dd8b2@spud \
--to=conor@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.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