From: Andrew Udvare <audvare@gmail.com>
To: alsa-devel@alsa-project.org
Subject: HDMI output with headphone jack sense possible on Conexant CX20561?
Date: Thu, 18 Mar 2010 15:05:25 -0400 [thread overview]
Message-ID: <201003181505.25291.audvare@gmail.com> (raw)
My audio codec is Conexant CX20561 (Hermosa) (haven't been able to find
anything about 'Hermosa' on the Wiki).
I'd like to be able to do a few things which I have not been able to do with
tutorials I found on the web:
- Whenever I plug in headphones, HDMI output is muted and headphones are
enabled
- Right now, the way I do this is by manually editing /etc/asound.conf to
have the following (commented out makes headphones work, not commented makes
HDMI work without any headphone/laptop speaker output)
/etc/asound.conf:
defaults.pcm.card 0
defaults.pcm.device 3
where 3 is my HDMI (IEC958 2; no idea what IEC958 1 is for) output. So I have
a switcher script that does the commenting and uncommenting. Would be nice if
this could be automatic (even if alsa had to run such a script on detecting
headphones).
- Route audio output (PCM) to input (for mixer recording) (Intel HDA cannot do
this apparently by default (thanks DRM), needs some hacking around?)
Information from alsa-info.sh: http://www.alsa-
project.org/db/?f=107f3f6012e68f04d3562d5e11aeb052a1454884
Are my model options correct?
And if it's important to know, I build ALSA in-kernel. Is this not
recommended? I know at the very least it makes it such that I have to reboot
to make any new options to take effect.
Thanks all
--
Andrew Udvare
audvare@gmail.com
978-870-5908
www.andyudvare.com
next reply other threads:[~2010-03-18 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 19:05 Andrew Udvare [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-18 15:09 HDMI output with headphone jack sense possible on Conexant CX20561? Andrew Udvare
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=201003181505.25291.audvare@gmail.com \
--to=audvare@gmail.com \
--cc=alsa-devel@alsa-project.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