On Mon, Apr 15, 2019 at 7:07 AM Maxime Ripard <maxime.ripard@xxxxxxxxxxx> wrote:
>
> Not all controllers using the A31 SPDIF binding actually have some RX
> capabilities, and therefore on some controllers we don't have the option to
> set an RX DMA channel.
>
> This was already done in the DTSI, but the binding itself was never
> updated.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@xxxxxxxxxxx>
> ---
> Documentation/devicetree/bindings/sound/allwinner,sun6i-a31-spdif.yaml | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/sound/allwinner,sun6i-a31-spdif.yaml b/Documentation/devicetree/bindings/sound/allwinner,sun6i-a31-spdif.yaml
> index 7329d9fcf34c..800f794fafe0 100644
> --- a/Documentation/devicetree/bindings/sound/allwinner,sun6i-a31-spdif.yaml
> +++ b/Documentation/devicetree/bindings/sound/allwinner,sun6i-a31-spdif.yaml
> @@ -44,14 +44,24 @@ properties:
> - const: spdif
>
> dmas:
> + minItems: 1
> + maxItems: 2
> items:
> - description: RX DMA Channel
> - description: TX DMA Channel
> + description:
> + Some controllers cannot receive but can only transmit data. In
> + such a case, the RX DMA channel is to be omitted.
Really, the schema is saying rx is optional, but it doesn't really
matter here as the schema for each item is just 'description'.
> dma-names:
> - items:
> - - const: rx
> - - const: tx
> + minItems: 1
> + maxItems: 2
> + enum:
> + - rx
> + - tx
> + description:
> + Some controllers cannot receive but can only transmit data. In
> + such a case, the RX name is to be omitted.
Here it matters though. This would allow just 'tx', '"tx", "tx"', or
either order.
You need something like this:
oneOf:
- items:
- const: rx
- const: tx
- const: tx
Ideally, we'd always put the required entry first and avoid this
problem. Not always possible if the first entry gets removed in later
h/w.
Rob
