From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
kernel@collabora.com,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 3/5] arm64: dts: mediatek: Add dtsi files to use rt5682s on mt8192
Date: Tue, 14 Feb 2023 11:25:54 +0100 [thread overview]
Message-ID: <09401672-3d4b-ef49-83e2-75abdcfb84bb@collabora.com> (raw)
In-Reply-To: <20230211002626.454844-4-nfraprado@collabora.com>
Il 11/02/23 01:26, Nícolas F. R. A. Prado ha scritto:
> Add a dtsi file for the rt5682s audio codec and another to wire it to be
> used by mt8192's sound card.
>
> These dtsi files will be used by Spherion rev4 and Hayato rev5-sku2,
> which make use of the rt5682s codec instead of the rt5682 used in
> previous revisions.
>
I think we're getting too many -audio-x devicetrees here... it's getting somehow
strange: imagine if we had 4 xxxx-audio-xxxx.dtsi for all of the supported
machines in dts/mediatek... that'd be at least *40* more files and would grow at
a quite fast pace. Too much IMO.
Check how I've done it in mt8195-cherry.dtsi, mt8195-cherry-tomato-r{1,2,3}.dts:
I didn't even have to add any mt8195-cherry-audio-xxxx.dtsi.
I understand your reasons for doing that - reducing duplication - but, in my
opinion, duplicating just 3 lines for 4 times is the way to go...
If those 4 files were used in *most MediaTek devicetrees* instead of one single
project, I'd agree with you though :-)
If you can come up with anything better than what I propose... I'd be even happier!
Cheers,
Angelo
next prev parent reply other threads:[~2023-02-14 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 0:26 [PATCH 0/5] arm64: dts: mediatek: Add newer revisions of Google Spherion and Hayato Nícolas F. R. A. Prado
2023-02-11 0:26 ` [PATCH 1/5] dt-bindings: arm64: dts: mediatek: Add rev5-sku2 of hayato Nícolas F. R. A. Prado
2023-02-11 11:43 ` Krzysztof Kozlowski
2023-02-14 10:26 ` AngeloGioacchino Del Regno
2023-02-11 0:26 ` [PATCH 2/5] dt-bindings: arm64: dts: mediatek: Add rev4 of spherion Nícolas F. R. A. Prado
2023-02-11 11:43 ` Krzysztof Kozlowski
2023-02-14 10:26 ` AngeloGioacchino Del Regno
2023-02-11 0:26 ` [PATCH 3/5] arm64: dts: mediatek: Add dtsi files to use rt5682s on mt8192 Nícolas F. R. A. Prado
2023-02-14 10:25 ` AngeloGioacchino Del Regno [this message]
2023-02-11 0:26 ` [PATCH 4/5] arm64: dts: mediatek: Add hayato-rev5-sku2 Nícolas F. R. A. Prado
2023-02-11 0:26 ` [PATCH 5/5] arm64: dts: mediatek: Add spherion-rev4 Nícolas F. R. A. Prado
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=09401672-3d4b-ef49-83e2-75abdcfb84bb@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.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=nfraprado@collabora.com \
--cc=robh+dt@kernel.org \
--cc=wenst@chromium.org \
/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
all inboxes | Powered by JetHome®