From: Dharma Balasubiramani <dharma.b@microchip.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>
Cc: <linux-mmc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-amlogic@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Dharma Balasubiramani <dharma.b@microchip.com>
Subject: [PATCH] dt-bindings: mmc: move compatible property to its specific binding
Date: Thu, 19 Dec 2024 09:40:41 +0530 [thread overview]
Message-ID: <20241219-mmc-slot-v1-1-dfc747a3d3fb@microchip.com> (raw)
Move the `compatible` property into its specific binding to make the MMC
slot more generic and modular.
Signed-off-by: Dharma Balasubiramani <dharma.b@microchip.com>
---
Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.yaml | 4 ++++
Documentation/devicetree/bindings/mmc/mmc-slot.yaml | 7 +------
2 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.yaml b/Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.yaml
index 022682a977c6..7600a4988eca 100644
--- a/Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.yaml
+++ b/Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.yaml
@@ -54,6 +54,10 @@ patternProperties:
A node for each slot provided by the MMC controller
properties:
+ compatible:
+ items:
+ - const: mmc-slot
+
reg:
enum: [0, 1, 2]
diff --git a/Documentation/devicetree/bindings/mmc/mmc-slot.yaml b/Documentation/devicetree/bindings/mmc/mmc-slot.yaml
index 1f0667828063..84c4605658e0 100644
--- a/Documentation/devicetree/bindings/mmc/mmc-slot.yaml
+++ b/Documentation/devicetree/bindings/mmc/mmc-slot.yaml
@@ -20,19 +20,15 @@ properties:
$nodename:
pattern: "^slot(@.*)?$"
- compatible:
- const: mmc-slot
-
reg:
description:
the slot (or "port") ID
maxItems: 1
required:
- - compatible
- reg
-unevaluatedProperties: false
+additionalProperties: true
examples:
- |
@@ -40,7 +36,6 @@ examples:
#address-cells = <1>;
#size-cells = <0>;
slot@0 {
- compatible = "mmc-slot";
reg = <0>;
bus-width = <4>;
};
---
base-commit: 7fa366f1b6e376c38966faa42da7f0f2e013fdab
change-id: 20241219-mmc-slot-0574889daea3
Best regards,
--
Dharma Balasubiramani <dharma.b@microchip.com>
next reply other threads:[~2024-12-19 4:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 4:10 Dharma Balasubiramani [this message]
2024-12-19 20:11 ` [PATCH] dt-bindings: mmc: move compatible property to its specific binding Conor Dooley
2025-01-07 3:34 ` Dharma.B
2025-01-07 20:34 ` Martin Blumenstingl
2025-01-08 3:11 ` Dharma.B
2025-01-08 20:56 ` Martin Blumenstingl
2025-01-20 4:30 ` Dharma.B
2025-02-04 4:24 ` Dharma.B
2025-02-04 8:14 ` neil.armstrong
2025-02-05 3:49 ` Dharma.B
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=20241219-mmc-slot-v1-1-dfc747a3d3fb@microchip.com \
--to=dharma.b@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@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