alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Paul Fertser <fercerpav@gmail.com>
To: Leon Romanovsky <leon@leon.nu>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"patch@alsa-project.org" <patch@alsa-project.org>,
	Stephen Warren <swarren@nvidia.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Marc Dietrich <marvin24@gmx.de>, Oliver Grawert <ogra@ubuntu.com>,
	Andrey Danin <danindrey@mail.ru>
Subject: Re: [PATCH] Add default config for tegra-alc5632 (as	found on paz00)
Date: Tue, 7 Feb 2012 16:54:04 +0400	[thread overview]
Message-ID: <20120207125404.GD11313@home.lan> (raw)
In-Reply-To: <CALq1K=+brR4OgPzfANKTFDoD-8Pbm0WjwXH+ZzShHvkGg6ntwA@mail.gmail.com>

On Tue, Feb 07, 2012 at 08:57:59AM +0200, Leon Romanovsky wrote:
> On Tue, Feb 7, 2012 at 07:52, Stephen Warren <swarren@nvidia.com> wrote:
> > On 02/06/2012 12:51 PM, Paul Fertser wrote:
> >> This makes paz00 (aka Toshiba ac100, a popular arm-based netbook) use
> >> dmix/dsnoop by default since it doesn't support hw mixing.
> >
> > This patch appears to match on card name being "tegra-alc5632", but the
> > device tree code that just got checked in will name the card "Compal
> > PAZ00" I believe. (and I believe this driver only supports DT not board
> > files) Am I missing something?
> Stephen, Mark,
> I want to raise our old question: "How do we need to call this card ?
> Do we need to call it tegra-alc5632, as was in pre-DT era ? Or do we
> need to call it "Compal PAZ00" as we introduced in DT patches ?".
> 
> The both names are applicable because "Compal PAZ00" is the name of
> notebook (hardware board) and tegra-alc5632 is the name of chips were
> used.

Since alsa-lib config file describes how to best deal with the
combination of chips rather than a particular notebook name
(especially given same device can have different names from different
vendors and at the same time some vendors are ill-minded enough to
call different devices with the same name) it would seem more logical
to stick to the chips' names.

Mark, do you have some idea how to solve the issue at hand (having
dmix on this netbook by default) better? Is quantity of maximum
simultaneous playback/record PCM streams already queryable by the
userspace? Somehow it happened that adding per-device config file was
ok during all these years, is there a better way now?

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com

  parent reply	other threads:[~2012-02-07 12:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 20:51 [PATCH] Add default config for tegra-alc5632 (as found on paz00) Paul Fertser
2012-02-07  5:52 ` Stephen Warren
2012-02-07  6:57   ` Leon Romanovsky
2012-02-07 11:26     ` Mark Brown
2012-02-07 12:54     ` Paul Fertser [this message]
2012-02-07 13:13       ` Mark Brown
2012-02-24  8:43         ` Paul Fertser
2012-02-27 16:32           ` Takashi Iwai
2012-02-07 11:45 ` Mark Brown

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=20120207125404.GD11313@home.lan \
    --to=fercerpav@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=danindrey@mail.ru \
    --cc=leon@leon.nu \
    --cc=marvin24@gmx.de \
    --cc=ogra@ubuntu.com \
    --cc=patch@alsa-project.org \
    --cc=swarren@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;
as well as URLs for NNTP newsgroup(s).