From: Mark Brown <broonie@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Yingkun Meng <mengyingkun@loongson.cn>,
Conor Dooley <conor@kernel.org>,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
conor+dt@kernel.org, lgirdwood@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, loongarch@lists.linux.dev,
loongson-kernel@lists.loongnix.cn
Subject: Re: [ PATCH v2 3/3] ASoC: dt-bindings: Add support for Loongson audio card
Date: Tue, 13 Jun 2023 14:54:36 +0100 [thread overview]
Message-ID: <449d07d9-5538-4f36-83a0-3a81a9ab9ea2@sirena.org.uk> (raw)
In-Reply-To: <20230613-depletion-garnet-ccc2009111c3@wendy>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
On Tue, Jun 13, 2023 at 01:46:41PM +0100, Conor Dooley wrote:
> So it is entirely a software construct? Why does it need a dt-binding
> then? Your commit message says the controller is present on the device!
A typical embedded (or power efficient laptop) audio design will consist
of multiple devices connected together (frequently via non-control
buses) together with system level passive components and plastics which
are also important to the audio configuration. A card binding describes
the interconections between the devices in the system and provides
identification information for the audio subsystem. This system level
audio integration is a physical thing that can be pointed at that
requires real software control.
Like I said before please look at the existing audio card bindings.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-06-13 13:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 8:56 [ PATCH v2 3/3] ASoC: dt-bindings: Add support for Loongson audio card YingKun Meng
2023-06-12 17:24 ` Conor Dooley
2023-06-13 12:23 ` Yingkun Meng
2023-06-13 12:28 ` Conor Dooley
2023-06-13 12:38 ` Yingkun Meng
2023-06-13 12:46 ` Conor Dooley
2023-06-13 13:03 ` Yingkun Meng
2023-06-13 13:54 ` Mark Brown [this message]
2023-06-13 14:29 ` Conor Dooley
2023-06-13 15:23 ` Mark Brown
2023-06-12 9:00 YingKun Meng
2023-06-13 8:36 ` Krzysztof Kozlowski
2023-06-14 9:25 ` Yingkun Meng
2023-06-13 8:43 ` Krzysztof Kozlowski
2023-06-14 9:27 ` Yingkun Meng
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=449d07d9-5538-4f36-83a0-3a81a9ab9ea2@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=mengyingkun@loongson.cn \
--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).