From: Neil Armstrong <neil.armstrong@linaro.org>
To: Jerome Brunet <jbrunet@baylibre.com>,
Christian Hewitt <christianshewitt@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: amlogic: add more basic audio support
Date: Fri, 8 Sep 2023 14:30:33 +0200 [thread overview]
Message-ID: <00436bd2-5f3c-4fd6-9db8-799c541c6a33@linaro.org> (raw)
In-Reply-To: <1jh6p0vdyj.fsf@starbuckisacylon.baylibre.com>
Hi,
On 15/08/2023 11:37, Jerome Brunet wrote:
>
> On Tue 15 Aug 2023 at 09:27, Christian Hewitt <christianshewitt@gmail.com> wrote:
>
>> This mini-series adds basic audio support to the P200/P201 (GXBB) and U200 (G12A)
>> reference boards. Few people likely have the original reference boards which have
>> extra audio capabilities, but the device-trees are widely [ab]used by users with
>> Android set-top boxes whose hardware is copy/pasted from the reference designs to
>> get working installs. Adding basic audio support does no harm to the real boards
>> and helps the secondary cause.
>
> Still, this is something you have not tested on the u200 reference
> design. I believe this was already discussed in the past.
>
> The u200 is far more complex when it comes to audio and certainly would
> not work on this no-name android device. These device are heavily
> "inspired" by the reference, but trimmed down in many aspect including
> audio capabilities - NOT copied.
I understand you point, but those changes only adds "internal" audio & basic spdif
capabilities so it won't affect the on-board audio electronics in any way.
>
> People abusing the u200 or p200 DT does make the patchset valid
This is a reality, but still I think this patchset is valid and I'll
pick those since they are used for years out-of-tree and probably works
very fine in the reference design boards.
Neil
>
>>
>> Christian Hewitt (3):
>> arm64: dts: meson: add audio playback to p200
>> arm64: dts: meson: add audio playback to p201
>> arm64: dts: meson: add audio playback to u200
>>
>> .../boot/dts/amlogic/meson-g12a-u200.dts | 129 ++++++++++++++++++
>> .../boot/dts/amlogic/meson-gxbb-p200.dts | 60 ++++++++
>> .../boot/dts/amlogic/meson-gxbb-p201.dts | 39 ++++++
>> 3 files changed, 228 insertions(+)
>
next prev parent reply other threads:[~2023-09-08 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 9:27 [PATCH 0/3] arm64: dts: amlogic: add more basic audio support Christian Hewitt
2023-08-15 9:27 ` [PATCH 1/3] arm64: dts: meson: add audio playback to p200 Christian Hewitt
2023-08-15 9:27 ` [PATCH 2/3] arm64: dts: meson: add audio playback to p201 Christian Hewitt
2023-08-15 9:27 ` [PATCH 3/3] arm64: dts: meson: add audio playback to u200 Christian Hewitt
2023-08-15 9:37 ` [PATCH 0/3] arm64: dts: amlogic: add more basic audio support Jerome Brunet
2023-09-08 12:30 ` Neil Armstrong [this message]
2023-09-11 9:46 ` Neil Armstrong
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=00436bd2-5f3c-4fd6-9db8-799c541c6a33@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).