[alsa-devel] 1.0.15: volume levels drift on HDA with STAC92XX codec

[Takashi Iwai]

At Mon, 5 Nov 2007 16:53:23 +0200,
Maxim Levitsky wrote:
> 
> On Monday 05 November 2007 13:40:48 Takashi Iwai wrote:
> > At Thu, 1 Nov 2007 20:17:30 +0200,
> > Maxim Levitsky wrote:
> > > 
> > > On Thursday 01 November 2007 19:47:39 Chuck Ebbert wrote:
> > > > We have two reports now of unstable volume levels:
> > > > 
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=361051
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=354981
> > > > 
> > > > This is with kernel 2.6.23 plus the two ALSA merge patches from
> > > > 2.6.23-rc1.
> > > > _______________________________________________
> > > > Alsa-devel mailing list
> > > > Alsa-devel at alsa-project.org
> > > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> > > > 
> > > Probably this isn't a software bug.
> > > Probably this chip country to datasheet doesn't have usable "Master
> >  > Volume" (volume knob) control.
> > > 
> > > 
> > > The master volume control wasn't present before, I added support for
> >  > it, using data-sheets. 
> > > I need to know what exactly sigmatel codec was used in both cases.
> > 
> > Yes, the latter case seems with STAC9205 but the former one (361051)
> > isn't clear.  Please check /proc/asound/card0/codec#* entries.
> > 
> > 
> > thanks,
> > 
> > Takashi
> > 
> 
> The former is also STAC9205/04/ since it is the only one with analog loopback and two ADCs
> 
> I have question, I talked with the reporter of 354981, and I don't know why but his amixer
> gives very strange results:
> 
> [root at itse68482 ~]# cat amixer-contents-kernel-2.6.23.2-36
> numid=0,iface=MIXER,name='Master Playback Switch'
>   ; type=BOOLEAN,access=rw------,values=1
>   : values=on
> numid=0,iface=MIXER,name='Master Playback Volume'
>   ; type=INTEGER,access=rw------,values=2,min=0,max=65536,step=1
>   : values=65536,65536
> numid=0,iface=MIXER,name='Capture Switch'
>   ; type=BOOLEAN,access=rw------,values=1
>   : values=on
> numid=0,iface=MIXER,name='Capture Volume'
>   ; type=INTEGER,access=rw------,values=2,min=0,max=65536,step=1
>   : values=34953,34953
> 
> How can that be?

Is the codec accessed properly?  This looks like the error at reading
amp capability of these NIDS and returned -1.  The volume attributes
are extracted from the amp caps.  But if so, usually relevant kernel
messages appear...


Takashi