Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kailang <kailang@realtek.com>
Cc: " (alsa-devel@alsa-project.org)" <alsa-devel@alsa-project.org>
Subject: Re: Dell USB audio driver workaround
Date: Wed, 06 Apr 2016 11:36:37 +0200	[thread overview]
Message-ID: <s5h37qzm63e.wl-tiwai@suse.de> (raw)
In-Reply-To: <6FAB7C47BCF00940BB0999A99BE3547A17A33059@RTITMBSV09.realtek.com.tw>

On Wed, 06 Apr 2016 11:22:43 +0200,
Kailang wrote:
> 
>  
> 
> > -----Original Message-----
> > From: Takashi Iwai [mailto:tiwai@suse.de] 
> > Sent: Wednesday, April 06, 2016 4:57 PM
> > To: Kailang
> > Cc: (alsa-devel@alsa-project.org)
> > Subject: Re: Dell USB audio driver workaround
> > 
> > On Wed, 06 Apr 2016 08:29:12 +0200,
> > Kailang wrote:
> > > 
> > > Hi Takashi,
> > > 
> > > Dell had USB dock.
> > > Maybe firmware issue, the master volume always keep at 0x57.
> > > Attach patch will fix it to keep at Max volume.
> > > 
> > > Could you help us to update it?
> > 
> > Well, I don't get how this patch works..
> > 
> > > diff --git a/sound/usb/mixer.c b/sound/usb/mixer.c index 
> > > 4f85757..84d9a4e 100644
> > > --- a/sound/usb/mixer.c
> > > +++ b/sound/usb/mixer.c
> > > @@ -846,6 +846,12 @@ static void volume_control_quirks(struct 
> > > usb_mixer_elem_info *cval,  {
> > >  	struct snd_usb_audio *chip = cval->head.mixer->chip;
> > >  	switch (chip->usb_id) {
> > > +	case USB_ID(0x0bda, 0x4014): /* Dell workaround */
> > > +		if (strstr(kctl->id.name, "Playback Volume") != NULL) {
> > > +			cval->min = 0x0000;
> > > +			cval->max = 0x0000;
> > > +		}
> > > +		break;
> > 
> > So, this means that this value has to be fixed to 0?
> > If yes, can't we simply remove this volume instead?
> 
> Yes, but it need to set Max volume to 0. This is test on my site.
> Because it will rewrite 0x57 value to codec register when driver is loaded.
> And keep 0x57 volume value all the time. So, Master volume will lower than windows machine.
> This case which driver fail to build the alsa mixer(This is firmware cause it). So, no hardware volume control on this.
> If the Max volume value is 0,  system will not set default value 0x57 for first time loading driver.

Which values (min/max) does this FU take and which values are buggy?
Judging from your description, the firmware gives the bogus max value
(white min value = 0) and a volume higher than zero is attenuation?


Takashi

  reply	other threads:[~2016-04-06  9:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6FAB7C47BCF00940BB0999A99BE3547A17A32FFC@RTITMBSV09.realtek.com.tw>
2016-04-06  8:56 ` Dell USB audio driver workaround Takashi Iwai
2016-04-06  9:22   ` Kailang
2016-04-06  9:36     ` Takashi Iwai [this message]
2016-04-07  7:05       ` Kailang
2016-04-07  9:26         ` Takashi Iwai
2016-04-07  9:45           ` Kailang
2016-04-07  9:53             ` Takashi Iwai
2016-04-07 10:13               ` Kailang
2016-04-07 10:07           ` Kailang
2016-04-07 10:18             ` Takashi Iwai
     [not found]               ` <6FAB7C47BCF00940BB0999A99BE3547A17A332FD@RTITMBSV09.realtek.com.tw>
2016-04-12  9:26                 ` Takashi Iwai
2017-06-14  2:29                   ` Hui Wang
2017-06-14 15:50                     ` Takashi Iwai
2017-06-15  9:40                       ` Hui Wang
2017-06-20 14:19                         ` Tanu Kaskinen
2017-06-21  0:05                           ` Hui Wang

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=s5h37qzm63e.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kailang@realtek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox