From: Rob Herring <robh@kernel.org>
To: Trevor Wu <trevor.wu@mediatek.com>
Cc: broonie@kernel.org, tiwai@suse.com, matthias.bgg@gmail.com,
alsa-devel@alsa-project.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
aaronyu@google.com, yc.hung@mediatek.com
Subject: Re: [PATCH 5/5] dt-bindings: mediatek: mt8195: add mt8195-mt6359-max98390-rt5682 document
Date: Thu, 10 Mar 2022 16:18:35 -0600 [thread overview]
Message-ID: <Yip5O3t0Ymyc2h+p@robh.at.kernel.org> (raw)
In-Reply-To: <20220308072435.22460-6-trevor.wu@mediatek.com>
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@mediatek.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@mediatek.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
next prev parent reply other threads:[~2022-03-10 22:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 7:24 [PATCH 0/5] ASoC: mediatek: Add support for MT8195 sound card with max98390 and rt5682 Trevor Wu
2022-03-08 7:24 ` [PATCH 1/5] ASoC: mediatek: mt8195: add reset controller Trevor Wu
2022-03-10 15:25 ` AngeloGioacchino Del Regno
2022-03-08 7:24 ` [PATCH 2/5] dt-bindings: mediatek: mt8195: add reset property Trevor Wu
2022-03-10 22:12 ` Rob Herring
2022-03-12 13:31 ` Trevor Wu
2022-03-08 7:24 ` [PATCH 3/5] ASoC: mediatek: mt8195: common code for mt8195 machine driver Trevor Wu
2022-03-08 7:24 ` [PATCH 4/5] ASoC: mediatek: mt8195: add machine driver with mt6359, max98390 and rt5682 Trevor Wu
2022-03-10 15:21 ` AngeloGioacchino Del Regno
2022-03-12 16:18 ` Trevor Wu
2022-03-14 9:00 ` AngeloGioacchino Del Regno
2022-03-08 7:24 ` [PATCH 5/5] dt-bindings: mediatek: mt8195: add mt8195-mt6359-max98390-rt5682 document Trevor Wu
2022-03-10 22:18 ` Rob Herring [this message]
2022-03-12 14:20 ` Trevor Wu
2022-03-14 15:28 ` Rob Herring
2022-03-11 20:22 ` (subset) [PATCH 0/5] ASoC: mediatek: Add support for MT8195 sound card with max98390 and rt5682 Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yip5O3t0Ymyc2h+p@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=aaronyu@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=tiwai@suse.com \
--cc=trevor.wu@mediatek.com \
--cc=yc.hung@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox