[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yip5O3t0Ymyc2h+p@robh.at.kernel.org>
Date: Thu, 10 Mar 2022 16:18:35 -0600
From: Rob Herring <robh@...nel.org>
To: Trevor Wu <trevor.wu@...iatek.com>
Cc: broonie@...nel.org, tiwai@...e.com, matthias.bgg@...il.com,
alsa-devel@...a-project.org, linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, aaronyu@...gle.com,
yc.hung@...iatek.com
Subject: Re: [PATCH 5/5] dt-bindings: mediatek: mt8195: add
mt8195-mt6359-max98390-rt5682 document
On Tue, Mar 08, 2022 at 03:24:35PM +0800, Trevor Wu wrote:
> This patch adds document for mt8195 board with mt6359, max98390 and
> rt5682.
>
> Signed-off-by: Trevor Wu <trevor.wu@...iatek.com>
> ---
> .../sound/mt8195-mt6359-max98390-rt5682.yaml | 61 +++++++++++++++++++
> 1 file changed, 61 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/mt8195-mt6359-max98390-rt5682.yaml
>
> diff --git a/Documentation/devicetree/bindings/sound/mt8195-mt6359-max98390-rt5682.yaml b/Documentation/devicetree/bindings/sound/mt8195-mt6359-max98390-rt5682.yaml
> new file mode 100644
> index 000000000000..7ec14d61b109
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/mt8195-mt6359-max98390-rt5682.yaml
> @@ -0,0 +1,61 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/mt8195-mt6359-max98390-rt5682.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Mediatek MT8195 with MT6359, MAX98390 and RT5682 ASoC sound card driver
> +
> +maintainers:
> + - Trevor Wu <trevor.wu@...iatek.com>
> +
> +description:
> + This binding describes the MT8195 sound card.
> +
> +properties:
> + compatible:
> + const: mediatek,mt8195_mt6359_max98390_rt5682
You have nodes for each of these components, why do we need new
compatible string for each combination. You can figure out the
combination by looking at each of those nodes.
Second, why does each combination need a new schema doc?
Rob
Powered by blists - more mailing lists