From: Matt Porter <mporter@embeddedalley.com>
To: Arnaud Patard <apatard@mandriva.com>
Cc: Matt Porter <mporter@embeddedalley.com>,
Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org
Subject: Re: HDA pin sense and presence detect capability
Date: Wed, 25 Jan 2006 10:14:22 -0700 [thread overview]
Message-ID: <20060125101422.D29602@cox.net> (raw)
In-Reply-To: <m3bqy0p7n9.fsf@anduin.mandrakesoft.com>; from apatard@mandriva.com on Wed, Jan 25, 2006 at 05:57:46PM +0100
On Wed, Jan 25, 2006 at 05:57:46PM +0100, Arnaud Patard wrote:
> Matt Porter <mporter@embeddedalley.com> writes:
>
> > On Wed, Jan 25, 2006 at 04:50:40PM +0100, Arnaud Patard wrote:
> >> About what's done in patch_sigmatel.c : what's the point of disabling
> >> the output ? imho, you only need to mute the nid.
> >
> > It seemed easier to disable the actual pin nid outputs for all line outs
> > (thing surround) than walk back to the associated DAC nids (which can
>
> I see... but afaik, muting the DAC is not the solution because you may
> have one DAC with the HP and speakers nids connected to it (for instance
> on the ad1981hd). My point was about muting the nid itself.
Indeed, that's the other reason for not doing it that way. What do
you mean by "muting the nid itself"? The pin widget nid? There's no
mute on the sigmatel codec pin widgets since there's no amp capability
there. Disabling the output is the way to mute at the pin widget...
at least on sigmatel hda codecs.
> > vary on sigmatel codecs) and mute those. It accomplishes the same
> > thing as muting...except there's no change in mixer state.
>
> Reflecting a change in the mixer state is more userfriendly but as long
> as it's working as the user expects, that's not a real worry.
Yeah, I wasn't sure about that. On the sigmatel codecs, the output
amps are in the DAC nids so we'd have to mute all of them in an
associated group if this is the desired userfriendly view of things.
Not a big deal to do, just not as simple as my first pass.
> >> Also, if there are several users of similar functions and on others chips than
> >> sigmatel, shouldn't it be better to put something in hda_codec.c ?
> >
> > I think so, but this was somewhat of an experimental first attempt
> > at this support. I just haven't had time to do much more with it yet.
>
> okay. I'm trying to have something working for my codec and then I'll
> try to work on this. If you don't agree, scream :)
I think it's great. Sounds like Takashi wants to see more shared
code as well and his opinion if far more important. ;)
-Matt
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next prev parent reply other threads:[~2006-01-25 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 15:34 HDA pin sense and presence detect capability Arnaud Patard
2006-01-25 15:43 ` Takashi Iwai
2006-01-25 15:50 ` Arnaud Patard
2006-01-25 16:01 ` Takashi Iwai
2006-01-25 16:08 ` Matt Porter
2006-01-25 16:57 ` Arnaud Patard
2006-01-25 17:14 ` Matt Porter [this message]
2006-01-25 17:32 ` Arnaud Patard
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=20060125101422.D29602@cox.net \
--to=mporter@embeddedalley.com \
--cc=alsa-devel@alsa-project.org \
--cc=apatard@mandriva.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.