295c894c37
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>
49 lines
942 B
YAML
49 lines
942 B
YAML
# SPDX-License-Identifier: GPL-2.0
|
|
%YAML 1.2
|
|
---
|
|
$id: http://devicetree.org/schemas/mmc/mmc-card.yaml#
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
|
|
|
title: MMC Card / eMMC Generic Device Tree Bindings
|
|
|
|
maintainers:
|
|
- Ulf Hansson <ulf.hansson@linaro.org>
|
|
|
|
description: |
|
|
This documents describes the devicetree bindings for a mmc-host controller
|
|
child node describing a mmc-card / an eMMC.
|
|
|
|
properties:
|
|
compatible:
|
|
const: mmc-card
|
|
|
|
reg:
|
|
const: 0
|
|
|
|
broken-hpi:
|
|
$ref: /schemas/types.yaml#/definitions/flag
|
|
description:
|
|
Use this to indicate that the mmc-card has a broken hpi
|
|
implementation, and that hpi should not be used.
|
|
|
|
required:
|
|
- compatible
|
|
- reg
|
|
|
|
additionalProperties: false
|
|
|
|
examples:
|
|
- |
|
|
mmc {
|
|
#address-cells = <1>;
|
|
#size-cells = <0>;
|
|
|
|
card@0 {
|
|
compatible = "mmc-card";
|
|
reg = <0>;
|
|
broken-hpi;
|
|
};
|
|
};
|
|
|
|
...
|