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 v2]ASoC:blackfin:add ad73311 card driver name
Date: Thu, 15 Sep 2011 11:00:37 +0100 [thread overview]
Message-ID: <20110915100036.GC7988@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAHG8p1CUveaYFkE+=FOZhTpPoKXTWB3UdTJpwtDq8pGTp17CzQ@mail.gmail.com>
On Wed, Sep 14, 2011 at 11:27:28AM +0800, Scott Jiang wrote:
> 2011/9/13 Mark Brown <broonie@opensource.wolfsonmicro.com>:
> > On Tue, Sep 13, 2011 at 02:59:26PM -0400, Scott Jiang wrote:
> > All my comments about the previous revision of the patch continue to
> > apply here. The changlog doesn't explain the issue well (the driver
> > should already end up with a unique name)
> in alsa lib snd_config_hook_load_for_all_cards(), use
> sndrv_ctl_card_info->driver to determine card config,
> not sndrv_ctl_card_info->name, though card name contains enough info.
So the issue isn't that the driver doesn't have a name, it's that you
don't like the name it was given. The changelog needs to explain this,
and also explain why this is an issue in this one driver.
> > and the name you've picked
> > is less distinctive than the existing name.
> I know the name is not good enough, but it is a historical result.
> Asoc copy codec name to card->driver before, cause all cards config
> file in alsa lib conf dir have this kind of name.
This sounds like you should fix userspace. It does go back to the issue
I regularly raise with the Blackfin code constantly assuming that there
can be a single driver which covers all combinations of a Blackfin CPU
with a given CODEC.
next prev parent reply other threads:[~2011-09-15 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 18:59 [PATCH v2]ASoC:blackfin:add ad73311 card driver name Scott Jiang
2011-09-13 10:53 ` Mark Brown
2011-09-14 3:27 ` Scott Jiang
2011-09-15 10:00 ` Mark Brown [this message]
2011-09-16 3:53 ` Scott Jiang
2011-09-16 9:47 ` Mark Brown
2011-09-13 16:11 ` Liam Girdwood
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=20110915100036.GC7988@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;
as well as URLs for NNTP newsgroup(s).