Message ID | 20220605133300.376161-2-mail@conchuod.ie |
---|---|
State | Superseded |
Headers | show |
Series | clear riscv dtbs_check errors | expand |
On 05/06/2022 15:32, mail@conchuod.ie wrote: > From: Conor Dooley <conor.dooley@microchip.com> > > Convert the mmc-spi-slot text based binding doc to yaml, > with the side effect of cleaning up some of the riscv > dtbs_check warnings. > > Signed-off-by: Conor Dooley <conor.dooley@microchip.com> > --- > .../devicetree/bindings/mmc/mmc-spi-slot.txt | 29 ------- > .../devicetree/bindings/mmc/mmc-spi-slot.yaml | 76 +++++++++++++++++++ > 2 files changed, 76 insertions(+), 29 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt > create mode 100644 Documentation/devicetree/bindings/mmc/mmc-spi-slot.yaml > > diff --git a/Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt b/Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt > deleted file mode 100644 > index 5e74db69f581..000000000000 > --- a/Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt > +++ /dev/null > @@ -1,29 +0,0 @@ > -MMC/SD/SDIO slot directly connected to a SPI bus > - > -This file documents differences between the core properties described > -by mmc.txt and the properties used by the mmc_spi driver. > - > -Required properties: > -- spi-max-frequency : maximum frequency for this device (Hz). > - > -Optional properties: > -- voltage-ranges : two cells are required, first cell specifies minimum > - slot voltage (mV), second cell specifies maximum slot voltage (mV). > - Several ranges could be specified. If not provided, 3.2v..3.4v is assumed. > -- gpios : may specify GPIOs in this order: Card-Detect GPIO, > - Write-Protect GPIO. Note that this does not follow the > - binding from mmc.txt, for historical reasons. > - > -Example: > - > - mmc-slot@0 { > - compatible = "fsl,mpc8323rdb-mmc-slot", > - "mmc-spi-slot"; > - reg = <0>; > - gpios = <&qe_pio_d 14 1 > - &qe_pio_d 15 0>; > - voltage-ranges = <3300 3300>; > - spi-max-frequency = <50000000>; > - interrupts = <42>; > - interrupt-parent = <&PIC>; > - }; > diff --git a/Documentation/devicetree/bindings/mmc/mmc-spi-slot.yaml b/Documentation/devicetree/bindings/mmc/mmc-spi-slot.yaml > new file mode 100644 > index 000000000000..a5fd723140c9 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mmc/mmc-spi-slot.yaml > @@ -0,0 +1,76 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/mmc/mmc-spi-slot.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: MMC/SD/SDIO slot directly connected to a SPI bus > + > +maintainers: > + - Ulf Hansson <ulf.hansson@linaro.org> > + > +allOf: > + - $ref: "mmc-controller.yaml" > + > +description: | > + The extra properties used by an mmc connected via spi. s/spi/SPI/ > + > +properties: > + compatible: > + const: "mmc-spi-slot" No quotes, please. > + > + reg: > + maxItems: 1 > + > + spi-max-frequency: true I think instead you should reference: /schemas/spi/spi-peripheral-props.yaml (because also other properties might be needed for different SPI controllers) > + > + interrupts: > + maxItems: 1 > + > + voltage-ranges: > + $ref: '/schemas/types.yaml#/definitions/uint32-matrix' Here as well - quotes are not needed. Some schemas have it, some not, but I guess shorter is preferred :) > + description: | > + Two cells are required, first cell specifies minimum slot voltage (mV), > + second cell specifies maximum slot voltage (mV). > + items: > + items: > + - description: | > + value for minimum slot voltage > + default: 3200 > + - description: | > + value for maximum slot voltage > + default: 3400 > + maxItems: 1 > + > + gpios: > + description: | > + For historical reasons, this does not follow the generic mmc-controller binding. > + minItems: 1 > + items: > + - description: Card-Detect GPIO > + - description: Write-Protect GPIO > + > +required: > + - compatible > + - reg > + - spi-max-frequency > + > +unevaluatedProperties: false > + > +examples: > + - | > + spi { > + #address-cells = <1>; > + #size-cells = <0>; > + mmc@0 { > + compatible = "mmc-spi-slot"; > + reg = <0>; > + gpios = <&qe_pio_d 14 1>, <&qe_pio_d 15 0>; The GPIO flags should be common defines instead. > + voltage-ranges = <3300 3300>; > + spi-max-frequency = <50000000>; > + interrupts = <42>; > + interrupt-parent = <&PIC>; > + }; > + }; > + > +... Best regards, Krzysztof
diff --git a/Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt b/Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt deleted file mode 100644 index 5e74db69f581..000000000000 --- a/Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt +++ /dev/null @@ -1,29 +0,0 @@ -MMC/SD/SDIO slot directly connected to a SPI bus - -This file documents differences between the core properties described -by mmc.txt and the properties used by the mmc_spi driver. - -Required properties: -- spi-max-frequency : maximum frequency for this device (Hz). - -Optional properties: -- voltage-ranges : two cells are required, first cell specifies minimum - slot voltage (mV), second cell specifies maximum slot voltage (mV). - Several ranges could be specified. If not provided, 3.2v..3.4v is assumed. -- gpios : may specify GPIOs in this order: Card-Detect GPIO, - Write-Protect GPIO. Note that this does not follow the - binding from mmc.txt, for historical reasons. - -Example: - - mmc-slot@0 { - compatible = "fsl,mpc8323rdb-mmc-slot", - "mmc-spi-slot"; - reg = <0>; - gpios = <&qe_pio_d 14 1 - &qe_pio_d 15 0>; - voltage-ranges = <3300 3300>; - spi-max-frequency = <50000000>; - interrupts = <42>; - interrupt-parent = <&PIC>; - }; diff --git a/Documentation/devicetree/bindings/mmc/mmc-spi-slot.yaml b/Documentation/devicetree/bindings/mmc/mmc-spi-slot.yaml new file mode 100644 index 000000000000..a5fd723140c9 --- /dev/null +++ b/Documentation/devicetree/bindings/mmc/mmc-spi-slot.yaml @@ -0,0 +1,76 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/mmc/mmc-spi-slot.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: MMC/SD/SDIO slot directly connected to a SPI bus + +maintainers: + - Ulf Hansson <ulf.hansson@linaro.org> + +allOf: + - $ref: "mmc-controller.yaml" + +description: | + The extra properties used by an mmc connected via spi. + +properties: + compatible: + const: "mmc-spi-slot" + + reg: + maxItems: 1 + + spi-max-frequency: true + + interrupts: + maxItems: 1 + + voltage-ranges: + $ref: '/schemas/types.yaml#/definitions/uint32-matrix' + description: | + Two cells are required, first cell specifies minimum slot voltage (mV), + second cell specifies maximum slot voltage (mV). + items: + items: + - description: | + value for minimum slot voltage + default: 3200 + - description: | + value for maximum slot voltage + default: 3400 + maxItems: 1 + + gpios: + description: | + For historical reasons, this does not follow the generic mmc-controller binding. + minItems: 1 + items: + - description: Card-Detect GPIO + - description: Write-Protect GPIO + +required: + - compatible + - reg + - spi-max-frequency + +unevaluatedProperties: false + +examples: + - | + spi { + #address-cells = <1>; + #size-cells = <0>; + mmc@0 { + compatible = "mmc-spi-slot"; + reg = <0>; + gpios = <&qe_pio_d 14 1>, <&qe_pio_d 15 0>; + voltage-ranges = <3300 3300>; + spi-max-frequency = <50000000>; + interrupts = <42>; + interrupt-parent = <&PIC>; + }; + }; + +...