From: Daniel Jacobowitz <drow@false.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Ganged volume
Date: Fri, 12 Jan 2007 11:34:12 -0500 [thread overview]
Message-ID: <20070112163412.GA27450@nevyn.them.org> (raw)
In-Reply-To: <s5hirfcgqrm.wl%tiwai@suse.de>
On Fri, Jan 12, 2007 at 05:21:17PM +0100, Takashi Iwai wrote:
> Thanks for the patch (and sorry for the delayed review). The code
> looks good now.
>
> One remaining concern is how we can integrate this with the existing
> ac97_quirk stuff. For example, if a quirk tweaking the master
> volume/switch is applied, this may conflict with the ganged volumes.
> In other words, the ganged controls should be applied _after_ the
> quirks.
>
> Then I'm considering whether it might be rather easier to implement
> the virtual master element from the beginning. Basically, the virtual
> master is required for almost all codec chips with the surround
> support, not only for VT161x. So, featuring this as default isn't bad
> in the end.
>
> Oh, also, TLV support is another thing to do.
> This should be relatively easy, though.
I agree on both points, but I don't think I can do it myself without
breaking lots of other cards. At this point, maybe someone else
is interested in picking up this patch?
Oh, and in that case, I will post the minimal bits for VT1617A
surround separately.
--
Daniel Jacobowitz
CodeSourcery
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-01-12 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 20:37 Ganged volume Daniel Jacobowitz
2007-01-02 3:51 ` Daniel Jacobowitz
2007-01-12 16:21 ` Takashi Iwai
2007-01-12 16:34 ` Daniel Jacobowitz [this message]
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=20070112163412.GA27450@nevyn.them.org \
--to=drow@false.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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