From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
DTML <devicetree@vger.kernel.org>, Takashi Iwai <tiwai@suse.de>,
Sameer Pujar <spujar@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Olof Johansson <olof@lixom.net>,
Thierry Reding <treding@nvidia.com>,
ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: linux-next: manual merge of the sound tree with the arm-soc tree
Date: Mon, 25 Feb 2019 16:43:38 +0000 [thread overview]
Message-ID: <20190225164338.GB13898@sirena.org.uk> (raw)
In-Reply-To: <CAK8P3a2Q7OAAYCU01TNpHR2SM7N=YunyqZEihSESnQwxzL5=Vg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1313 bytes --]
On Mon, Feb 25, 2019 at 02:38:50PM +0100, Arnd Bergmann wrote:
> On Mon, Feb 25, 2019 at 12:24 PM Sameer Pujar <spujar@nvidia.com> wrote:
> > The motivation for adding custom sound card name is following,
> > 1. When for boards, multiple HDMI/DP ports are exposed, it is sometimes
> > necessary to know the default port or any customization for that matter.
> > Audio userspace can distinguish based on the sound card names.
> > 2. Multiple sound cards can coexist for a platform, the indication of
> > particular
> > audio path is useful.
> > 3. It can help to customize audio paths.
> > Generally people use "*,model" property in DT to name the sound complex.
> > Ex: "samsung,model" [sound/soc/samsung/snow.c]
> > "rockchip,model" [sound/soc/rockchip/rockchip_rt5645.c]
It's also useful since sound cards can be electically identical but
prefer different configuration due to the plastics (eg, a smaller
speaker was fitted, different outputs have different labels or playing
the speaker at full volume causes some models to have unpleasant effects
while others handle it fine).
> My impression here is that the idea of passing a model name
> through DT is well established, but for new stuff, we probably
> want to standardize on plain "model" rather than "$vendor,model".
Yes.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-25 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 1:36 linux-next: manual merge of the sound tree with the arm-soc tree Stephen Rothwell
2019-02-25 9:19 ` Arnd Bergmann
2019-02-25 11:14 ` Takashi Iwai
2019-02-25 11:24 ` Sameer Pujar
2019-02-25 13:38 ` Arnd Bergmann
2019-02-25 16:43 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-16 4:58 Stephen Rothwell
2024-09-16 8:42 ` Uwe Kleine-König
2024-09-17 23:57 ` Stephen Rothwell
2023-02-17 0:23 Stephen Rothwell
2023-02-20 22:27 ` Stephen Rothwell
2023-02-21 22:12 ` Stephen Rothwell
2011-10-11 4:43 Stephen Rothwell
2011-10-11 6:15 ` Ujfalusi, Peter
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=20190225164338.GB13898@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=spujar@nvidia.com \
--cc=tiwai@suse.de \
--cc=treding@nvidia.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