[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2249cf46-5c54-2e59-f247-5a22f2e6e5b9@canonical.com>
Date: Wed, 16 Feb 2022 11:29:46 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Mohan Kumar <mkumard@...dia.com>, broonie@...nel.org,
lgirdwood@...il.com, robh+dt@...nel.org, thierry.reding@...il.com,
tiwai@...e.com, jonathanh@...dia.com, spujar@...dia.com
Cc: alsa-devel@...a-project.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 5/6] dt-bindings: Document Tegra234 HDA support
On 16/02/2022 10:22, Mohan Kumar wrote:
> Update binding document for HDA support on Tegra234 chip.
>
> Tegra234 has max of 2 clocks and 2 resets which requires to add
> minItems and maxItems for clocks and resets as Tegra chips can
> now have minimum of 2 and maximum of 3 clocks and reset support.
>
> Signed-off-by: Mohan Kumar <mkumard@...dia.com>
> ---
> .../devicetree/bindings/sound/nvidia,tegra30-hda.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.yaml b/Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.yaml
> index 2c913aa44fee..12c31b4b99e1 100644
> --- a/Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.yaml
> +++ b/Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.yaml
> @@ -23,6 +23,7 @@ properties:
> - const: nvidia,tegra30-hda
> - items:
> - enum:
> + - nvidia,tegra234-hda
Why putting it in non-alphabetical order? Although someone put
nvidia,tegra124-hda already at the end of list... having things ordered
is helpful to avoid conflicts and makes code easier to read.
Best regards,
Krzysztof
Powered by blists - more mailing lists