summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/mmc/mmc-card.txt
diff options
context:
space:
mode:
authorMaxime Ripard <maxime@cerno.tech>2021-09-01 12:18:30 +0300
committerUlf Hansson <ulf.hansson@linaro.org>2021-10-12 11:21:16 +0300
commit295c894c37f7cf075dc5cf044e45fb781936fa50 (patch)
treec06708201bdfd03dc7cadaf9656b1120b43074bb /Documentation/devicetree/bindings/mmc/mmc-card.txt
parent9c1aaec47527816877befb7f18ea1cf25e55b8c8 (diff)
downloadlinux-295c894c37f7cf075dc5cf044e45fb781936fa50.tar.xz
dt-bindings: mmc: Convert MMC Card binding to a schema
MMC Cards can have an optional Device Tree binding to add non-discoverable properties. Now that we have the DT validation in place, let's convert the device tree bindings for that driver over to a YAML schema. Some of these properties were already described in the MMC controller binding, even though they are not generic and do not apply to any device, so we took the occasion to fix this. Cc: linux-mmc@vger.kernel.org Cc: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Maxime Ripard <maxime@cerno.tech> Reviewed-by: Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20210901091852.479202-31-maxime@cerno.tech Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'Documentation/devicetree/bindings/mmc/mmc-card.txt')
-rw-r--r--Documentation/devicetree/bindings/mmc/mmc-card.txt30
1 files changed, 0 insertions, 30 deletions
diff --git a/Documentation/devicetree/bindings/mmc/mmc-card.txt b/Documentation/devicetree/bindings/mmc/mmc-card.txt
deleted file mode 100644
index 8d2d71758907..000000000000
--- a/Documentation/devicetree/bindings/mmc/mmc-card.txt
+++ /dev/null
@@ -1,30 +0,0 @@
-mmc-card / eMMC bindings
-------------------------
-
-This documents describes the devicetree bindings for a mmc-host controller
-child node describing a mmc-card / an eMMC, see "Use of Function subnodes"
-in mmc.txt
-
-Required properties:
--compatible : Must be "mmc-card"
--reg : Must be <0>
-
-Optional properties:
--broken-hpi : Use this to indicate that the mmc-card has a broken hpi
- implementation, and that hpi should not be used
-
-Example:
-
-&mmc2 {
- pinctrl-names = "default";
- pinctrl-0 = <&mmc2_pins_a>;
- vmmc-supply = <&reg_vcc3v3>;
- bus-width = <8>;
- non-removable;
-
- mmccard: mmccard@0 {
- reg = <0>;
- compatible = "mmc-card";
- broken-hpi;
- };
-};