From: Andreas Kemnade <andreas@kemnade.info>
To: ulf.hansson@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com, linux-mmc@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Andreas Kemnade <andreas@kemnade.info>
Subject: [PATCH] dt-bindings: mmc: fsl-imx-esdhc: allow more compatible combinations
Date: Thu, 5 Jan 2023 22:38:56 +0100 [thread overview]
Message-ID: <20230105213856.1828360-1-andreas@kemnade.info> (raw)
Currently make dtbs_check shows lots of errors because imx*.dtsi does
not use single compatibles but combinations of them.
Allow all the combinations used there.
Patches fixing the dtsi files according to binding documentation were
submitted multiple times and are commonly rejected, so relax the rules.
Example:
https://lore.kernel.org/linux-devicetree/72e1194e10ccb4f87aed96265114f0963e805092.camel@pengutronix.de/
Reason: compatibility of new dtbs with old kernels or bootloaders.
This will significantly reduce noise on make dtbs_check.
Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
---
.../bindings/mmc/fsl-imx-esdhc.yaml | 24 +++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml b/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml
index dc6256f04b42..118ebb75f136 100644
--- a/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml
+++ b/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml
@@ -37,6 +37,30 @@ properties:
- fsl,imx8mm-usdhc
- fsl,imxrt1050-usdhc
- nxp,s32g2-usdhc
+ - items:
+ - const: fsl,imx50-esdhc
+ - const: fsl,imx53-esdhc
+ - items:
+ - const: fsl,imx6sl-usdhc
+ - const: fsl,imx6q-usdhc
+ - items:
+ - const: fsl,imx6sll-usdhc
+ - const: fsl,imx6sx-usdhc
+ - items:
+ - const: fsl,imx6sx-usdhc
+ - const: fsl,imx6sl-usdhc
+ - items:
+ - const: fsl,imx6ul-usdhc
+ - const: fsl,imx6sx-usdhc
+ - items:
+ - const: fsl,imx6ull-usdhc
+ - const: fsl,imx6sx-usdhc
+ - items:
+ - const: fsl,imx7d-usdhc
+ - const: fsl,imx6sl-usdhc
+ - items:
+ - const: fsl,imx7ulp-usdhc
+ - const: fsl,imx6sx-usdhc
- items:
- enum:
- fsl,imx8mq-usdhc
--
2.30.2
next reply other threads:[~2023-01-05 21:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 21:38 Andreas Kemnade [this message]
2023-01-06 8:41 ` [PATCH] dt-bindings: mmc: fsl-imx-esdhc: allow more compatible combinations Krzysztof Kozlowski
2023-01-06 19:33 ` Andreas Kemnade
2023-01-07 13:23 ` Krzysztof Kozlowski
2023-01-07 13:43 ` Andreas Kemnade
2023-01-07 14:00 ` Krzysztof Kozlowski
2023-01-07 14:07 ` Andreas Kemnade
2023-01-07 14:09 ` Krzysztof Kozlowski
2023-01-07 15:01 ` Andreas Kemnade
2023-01-07 15:07 ` Krzysztof Kozlowski
2023-01-07 15:54 ` Andreas Kemnade
2023-01-08 14:45 ` Krzysztof Kozlowski
2023-01-08 17:20 ` Andreas Kemnade
2023-01-09 9:14 ` Krzysztof Kozlowski
2023-01-08 22:46 ` Rob Herring
2023-01-09 23:15 ` Andreas Kemnade
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=20230105213856.1828360-1-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@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).