[alsa-devel] [PATCH] Sigmatel stac92hd71b7 low HP volume

Takashi Iwai tiwai at suse.de
Wed Oct 8 08:36:59 CEST 2008


At Wed, 8 Oct 2008 00:41:27 +0200,
Klaas De Craemer wrote:
> 
> On Tue, Oct 7, 2008 at 12:07 PM, Takashi Iwai <tiwai at suse.de> wrote:
> > At Tue, 7 Oct 2008 11:46:58 +0200,
> > Klaas De Craemer wrote:
> >>
> >> On Tue, Oct 7, 2008 at 7:44 AM, Takashi Iwai <tiwai at suse.de> wrote:
> >> > At Mon, 6 Oct 2008 19:10:14 +0200,
> >> > Klaas De Craemer wrote:
> >> >>
> >> >> On Mon, Oct 6, 2008 at 12:57 PM, Takashi Iwai <tiwai at suse.de> wrote:
> >> >> > [please don't drop Cc to alsa-devel ML]
> >> >> >
> >> >> > At Mon, 6 Oct 2008 12:48:43 +0200,
> >> >> > Klaas De Craemer wrote:
> >> >> >>
> >> >> >> Hello,
> >> >> >>
> >> >> >> I'm sure that the audioquality will degrade somewhat because of the additional amplification,
> >> >> >> but before, the HP-out was not usable at all. I had to use an external ampli just to use my
> >> >> >> headphones, even after turning all volume sliders to 100%. Then again, when removing the HP,
> >> >> >> the volume though the internal speakers was way too loud...
> >> >> >>
> >> >> >> I'm not sure what you mean with the output pin and headphone control, but I have uploaded the
> >> >> >> output of the codegraph tool before and after my modification here:
> >> >> >> http://users.vtk.be/~s0159120/codec_original.svg
> >> >> >> http://users.vtk.be/~s0159120/codec_final.svg
> >> >> >>
> >> >> >> Below is the output of alsa-info with the patched module
> >> >> >> Klaas
> >> >> >
> >> >> > Thanks.
> >> >> >
> >> >> > So, if I understand correctly, when the pin 0x0a is connected directly
> >> >> > from DAC0 0x10, the output level is too low even if you set the all
> >> >> > volumes maximal.
> >> >>
> >> >> That is correct.
> >> >>
> >> >>
> >> >> > In the alsa-info.sh output, I see the following:
> >> >> >> Node 0x10 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L
> >> >> >>   Amp-Out caps: N/A
> >> >> >>   Amp-Out vals:  [0x5e 0x5e]
> >> >> >
> >> >> > which means that you decrease the output level intentionally.
> >> >> > Is the HP output still too low even if you set to the higher value?
> >> >>
> >> >>
> >> >> No, after the patch I don't need 100% anymore.
> >> >
> >> > Of course not :)
> >> >
> >> >> The HP output is fine
> >> >> now, and I can tune it up and down a bit. Before using the mixer-amp,
> >> >> going from 90 to 100 resulted in going from no sound to little sound.
> >> >> Now the range is more useful.
> >> >
> >> > Could you check the raw value of the widget 0x10 without your patch?
> >> > The percent doesn't tell you exactly what you changed.
> >> >
> >> >
> >> > Takashi
> >> >
> >>
> >> I have pasted the output of /proc/asound/card0/codec#0 below, without
> >> the patch. However, I'm not sure what you're exactly looking for? I'm
> >> quite new to all this stuff , but I'd be more than happy to help out
> >> more, so feel free to ask anything.
> >
> > The mixer volume level in percentage might be different from the raw
> > value of the NID 0x10 (or 0x11?) amps because of volume-knob stuff.
> > I just wanted to make sure that a really high value is set to the
> > amp.
> >
> > OTOH, if it happens only with the headphone (I suppose the loud enough
> > output from the speaker after unplugging the headphone), this isn't a
> > matter of the DAC amp value.
> 
> 
> But, with this information, can something be done about it in future
> releases? Maybe a model-option?

Possibly.  Or, it's a generic problem regarding volume-knob.  It's not
ruled out yet.

> I also checked the output by connecting earplugs and by using the jack
> as lineout to my hifi, but it is again quite low-volume. So that rules
> out a "bad" headphone.

I didn't doubt it.  My question was "what is the raw value".
I don't trust the mixer percentage values you showed.  They are
important in the end result, but not for analyzing the problem.
Instead, the raw values the driver sends to the codec are really raw
and more understandable.  (And, for checking this, you can use
hda-verb program, too.)

So, if you try to analyze the problem, always check the values in
codec proc.  At best, check the values directly by yourself via
hda-verb program.


> Klaas
> 
> ps: it also seems like most of this conversation is not listed in the
> alsa-devel list?

The posts from non-subscribers have to be approved manually.
Just subscribe to the list first to reduce the latency.


thanks,

Takashi


More information about the Alsa-devel mailing list