From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Marek Vasut <marex@denx.de>
Cc: Anson Huang <Anson.Huang@nxp.com>,
Fabio Estevam <festevam@denx.de>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Oleksij Rempel <linux@rempel-privat.de>,
Peng Fan <peng.fan@nxp.com>, Rob Herring <robh+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org, Marek Vasut <marex@denx.de>
Subject: Re: [PATCH] dt-bindings: nvmem: snvs-lpgpr: Fix i.MX8M compatible strings
Date: Thu, 03 Nov 2022 09:19:34 +0100 [thread overview]
Message-ID: <2386257.iZASKD2KPV@steina-w> (raw)
In-Reply-To: <20221102222543.153026-1-marex@denx.de>
Am Mittwoch, 2. November 2022, 23:25:43 CET schrieb Marek Vasut:
> The compatible strings for "fsl,imx8m*-snvs-lpgpr" always contain
> the fallback "fsl,imx7d-snvs-lpgpr" compatible in DTs too, since
> the fallback compatible is what the driver matches on, this way:
> compatible = "fsl,imx8mm-snvs-lpgpr", "fsl,imx7d-snvs-lpgpr"
> The older "fsl,imx7d-snvs-lpgpr" and "fsl,imx6*-snvs-lpgpr" used
> only that single compatible string.
>
> Document both options in the binding document.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Anson Huang <Anson.Huang@nxp.com>
> Cc: Fabio Estevam <festevam@denx.de>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> Cc: Oleksij Rempel <linux@rempel-privat.de>
> Cc: Peng Fan <peng.fan@nxp.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: NXP Linux Team <linux-imx@nxp.com>
> Cc: devicetree@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
> ---
> .../devicetree/bindings/nvmem/snvs-lpgpr.yaml | 20 +++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/snvs-lpgpr.yaml
> b/Documentation/devicetree/bindings/nvmem/snvs-lpgpr.yaml index
> e374aa7891ae7..ec20e33d9b8f8 100644
> --- a/Documentation/devicetree/bindings/nvmem/snvs-lpgpr.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/snvs-lpgpr.yaml
> @@ -11,14 +11,18 @@ maintainers:
>
> properties:
> compatible:
> - enum:
> - - fsl,imx6q-snvs-lpgpr
> - - fsl,imx6ul-snvs-lpgpr
> - - fsl,imx7d-snvs-lpgpr
> - - fsl,imx8mm-snvs-lpgpr
> - - fsl,imx8mn-snvs-lpgpr
> - - fsl,imx8mp-snvs-lpgpr
> - - fsl,imx8mq-snvs-lpgpr
> + oneOf:
> + - items:
> + - enum:
> + - fsl,imx8mm-snvs-lpgpr
> + - fsl,imx8mn-snvs-lpgpr
> + - fsl,imx8mp-snvs-lpgpr
> + - fsl,imx8mq-snvs-lpgpr
> + - const: fsl,imx7d-snvs-lpgpr
> + - enum:
> + - fsl,imx6q-snvs-lpgpr
> + - fsl,imx6ul-snvs-lpgpr
> + - fsl,imx7d-snvs-lpgpr
>
> required:
> - compatible
Acked-by: Alexander Stein <alexander.stein@ew.tq-group.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Marek Vasut <marex@denx.de>
Cc: Anson Huang <Anson.Huang@nxp.com>,
Fabio Estevam <festevam@denx.de>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Oleksij Rempel <linux@rempel-privat.de>,
Peng Fan <peng.fan@nxp.com>, Rob Herring <robh+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org, Marek Vasut <marex@denx.de>
Subject: Re: [PATCH] dt-bindings: nvmem: snvs-lpgpr: Fix i.MX8M compatible strings
Date: Thu, 03 Nov 2022 09:19:34 +0100 [thread overview]
Message-ID: <2386257.iZASKD2KPV@steina-w> (raw)
In-Reply-To: <20221102222543.153026-1-marex@denx.de>
Am Mittwoch, 2. November 2022, 23:25:43 CET schrieb Marek Vasut:
> The compatible strings for "fsl,imx8m*-snvs-lpgpr" always contain
> the fallback "fsl,imx7d-snvs-lpgpr" compatible in DTs too, since
> the fallback compatible is what the driver matches on, this way:
> compatible = "fsl,imx8mm-snvs-lpgpr", "fsl,imx7d-snvs-lpgpr"
> The older "fsl,imx7d-snvs-lpgpr" and "fsl,imx6*-snvs-lpgpr" used
> only that single compatible string.
>
> Document both options in the binding document.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Anson Huang <Anson.Huang@nxp.com>
> Cc: Fabio Estevam <festevam@denx.de>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> Cc: Oleksij Rempel <linux@rempel-privat.de>
> Cc: Peng Fan <peng.fan@nxp.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: NXP Linux Team <linux-imx@nxp.com>
> Cc: devicetree@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
> ---
> .../devicetree/bindings/nvmem/snvs-lpgpr.yaml | 20 +++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/snvs-lpgpr.yaml
> b/Documentation/devicetree/bindings/nvmem/snvs-lpgpr.yaml index
> e374aa7891ae7..ec20e33d9b8f8 100644
> --- a/Documentation/devicetree/bindings/nvmem/snvs-lpgpr.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/snvs-lpgpr.yaml
> @@ -11,14 +11,18 @@ maintainers:
>
> properties:
> compatible:
> - enum:
> - - fsl,imx6q-snvs-lpgpr
> - - fsl,imx6ul-snvs-lpgpr
> - - fsl,imx7d-snvs-lpgpr
> - - fsl,imx8mm-snvs-lpgpr
> - - fsl,imx8mn-snvs-lpgpr
> - - fsl,imx8mp-snvs-lpgpr
> - - fsl,imx8mq-snvs-lpgpr
> + oneOf:
> + - items:
> + - enum:
> + - fsl,imx8mm-snvs-lpgpr
> + - fsl,imx8mn-snvs-lpgpr
> + - fsl,imx8mp-snvs-lpgpr
> + - fsl,imx8mq-snvs-lpgpr
> + - const: fsl,imx7d-snvs-lpgpr
> + - enum:
> + - fsl,imx6q-snvs-lpgpr
> + - fsl,imx6ul-snvs-lpgpr
> + - fsl,imx7d-snvs-lpgpr
>
> required:
> - compatible
Acked-by: Alexander Stein <alexander.stein@ew.tq-group.com>
next prev parent reply other threads:[~2022-11-03 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 22:25 [PATCH] dt-bindings: nvmem: snvs-lpgpr: Fix i.MX8M compatible strings Marek Vasut
2022-11-02 22:25 ` Marek Vasut
2022-11-03 8:19 ` Alexander Stein [this message]
2022-11-03 8:19 ` Alexander Stein
2022-11-03 13:55 ` Krzysztof Kozlowski
2022-11-03 13:55 ` Krzysztof Kozlowski
2022-11-11 6:24 ` Shawn Guo
2022-11-11 6:24 ` Shawn Guo
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=2386257.iZASKD2KPV@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=Anson.Huang@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux@rempel-privat.de \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.