[alsa-devel] HDA Analyzer

Takashi Iwai tiwai at suse.de
Fri Nov 28 17:59:51 CET 2008


At Fri, 28 Nov 2008 17:32:05 +0100 (CET),
Jaroslav Kysela wrote:
> 
> On Fri, 28 Nov 2008, Takashi Iwai wrote:
> 
> > At Fri, 28 Nov 2008 17:08:16 +0100 (CET),
> > Jaroslav Kysela wrote:
> > > 
> > > On Fri, 28 Nov 2008, Takashi Iwai wrote:
> > > 
> > > > > >   Node 0x22 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
> > > > > >     Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> > > > > >     Amp-In vals: [0x00 0x00] [0x80 0x80] [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
> > > > > >     Amp-Out caps: N/A
> > > > > >     Amp-Out vals: [0x00 0x00]
> > > > > 		    ^^^^^^^^^^^
> > > > > 
> > > > > It looks wrong, but I'm not a big expert for HDA codecs. Are amp values 
> > > > > available/writable when caps are N/A?
> > > > 
> > > > There is a global amp-cap definition.
> > > 
> > > OK, so it would be better to show the global amp-cap definition in the 
> > > GUI with a "copy" identification. Thanks.
> > 
> > Not really.  The amp-caps in each node show the capability overrides.
> > If you copy the output, you don't know whether it's an override
> > (although the same value) or a local one.
> 
> I put ' (Global)' suffix to the frame label when global caps are used in 
> my local source tree. So it should be clear for users.

OK, but please don't change the proc output.


Takashi


More information about the Alsa-devel mailing list