From: Pavel Hofman <pavel.hofman@ivitera.com>
To: pl bossart <bossart.nospam@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: IEC switch issues
Date: Wed, 23 Jun 2010 10:55:52 +0200 [thread overview]
Message-ID: <4C21CC18.3030200@ivitera.com> (raw)
In-Reply-To: <AANLkTinpl5hs7NRAm38uF7FbGCOuIOxCvohD70jOQxam@mail.gmail.com>
pl bossart napsal(a):
> If I play my AC3 data on my HDAudio/SPDIF output using the hw:0,1
> device, I can use alsamixer/amixer to mute/unmute.
>
> [ume@plb PassThough]$ amixer cset numid=12 on
> numid=12,iface=MIXER,name='IEC958 Playback Switch'
> ; type=BOOLEAN,access=rw------,values=1
> : values=on
> [ume@plb PassThough]$ amixer cset numid=12 off
> numid=12,iface=MIXER,name='IEC958 Playback Switch'
> ; type=BOOLEAN,access=rw------,values=1
> : values=off
>
> Now if I use the iec958: plugin, I can't control the mute switch any longer:
> [ume@plb PassThough]$ amixer cset numid=12 off
> amixer: Control default element write error: Operation not permitted
>
> [ume@plb PassThough]$ amixer cset numid=12 on
> amixer: Control default element write error: Operation not permitted
>
> What could possibly cause this issue? the IEC plugin relies on the
> device 1, am I missing something here?
> Thanks for your help
> - Pierre
Hi Pierre,
Check the config files in /usr/share/alsa/cards, probably HDA-Intel.conf
in your case, specifically the hooks section of its iec958 device
definition. It reads:
hooks.0 {
type ctl_elems
hook_args [
{
name "IEC958 Playback Default"
lock true
preserve true
value [ $AES0 $AES1 $AES2 $AES3 ]
}
{
name "IEC958 Playback Switch"
lock true
preserve true
value true
}
]
}
You can play with the "lock" directive.
Best regards,
Pavel.
next prev parent reply other threads:[~2010-06-23 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 21:22 IEC switch issues pl bossart
2010-06-23 8:55 ` Pavel Hofman [this message]
2010-06-23 12:05 ` Clemens Ladisch
2010-06-23 13:21 ` Raymond Yau
2010-06-23 15:01 ` pl bossart
2010-06-23 15:10 ` Clemens Ladisch
2010-06-23 17:04 ` pl bossart
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=4C21CC18.3030200@ivitera.com \
--to=pavel.hofman@ivitera.com \
--cc=alsa-devel@alsa-project.org \
--cc=bossart.nospam@gmail.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 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.