From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Scott Jiang <scott.jiang.linux@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
uclinux-dist-devel@blackfin.uclinux.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] alsa-lib: if card driver name is empty string, use card name instead
Date: Tue, 20 Sep 2011 11:53:33 +0100 [thread overview]
Message-ID: <20110920105333.GG2387@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAHG8p1AB_uxYdhThm+cgf+RdRtrKG4a_7g4j_R_h8VEU5ZUd9A@mail.gmail.com>
On Tue, Sep 20, 2011 at 06:36:15PM +0800, Scott Jiang wrote:
> 2011/9/20 Mark Brown <broonie@opensource.wolfsonmicro.com>:
> > - This clearly isn't something that affects only one driver - no ASoC
> > driver sets a driver name - so a change to a single driver is clearly
> > not a good solution even for just Blackfin.
> I thought about this. I wanted to copy codec name to driver name as
> before in asoc but I don't think it's a good idea.
> Now we can have multicodecs in one card, they may not be the same, right?
> If yes, we should add this name in each snd_soc_card.
If we want to do that then we need to go round every single machine
driver and add a driver name, plus add code in the core which flags
cards that don't set one.
next prev parent reply other threads:[~2011-09-20 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 17:15 [PATCH] alsa-lib: if card driver name is empty string, use card name instead Scott Jiang
2011-09-20 6:24 ` Takashi Iwai
2011-09-20 6:37 ` Scott Jiang
2011-09-20 6:39 ` Takashi Iwai
2011-09-20 6:55 ` Scott Jiang
2011-09-20 7:12 ` Takashi Iwai
2011-09-20 10:03 ` Mark Brown
2011-09-20 10:36 ` Scott Jiang
2011-09-20 10:53 ` Mark Brown [this message]
2011-09-20 10:14 ` Mark Brown
2011-09-20 10:33 ` Takashi Iwai
2011-09-20 10:51 ` Mark Brown
2011-09-20 10:58 ` Takashi Iwai
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=20110920105333.GG2387@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=scott.jiang.linux@gmail.com \
--cc=tiwai@suse.de \
--cc=uclinux-dist-devel@blackfin.uclinux.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