Re: [Ubuntu PATCH] ALSA: Add hp_only quirk for pci id [161f:2032] to via82xx

From: Takashi Iwai
Date: Fri Jun 16 2006 - 10:21:34 EST


At Thu, 15 Jun 2006 13:00:49 -0700,
Randy Dunlap wrote:
>
> From: crimsun@xxxxxxxxxxxx <crimsun@xxxxxxxxxxxx>
>
> [UBUNTU:sound/pci/] Add hp_only quirk for pci id [161f:2032] to via82xx ALSA driver
>
> http://www.kernel.org/git/?p=linux/kernel/git/bcollins/ubuntu-dapper.git;a=commitdiff;h=eae2cc78de39502595f67b7fc1f821f5963bb8ae
>
> UpstreamStatus: Not merged
>
> Christian Bjalevik reports in LP#38546 that his sound chipset requires
> the "hp_only" quirk to allow him to control sound volume correctly when
> headphones are inserted. This patch adds the appropriate pci id to the
> via82xx ALSA driver so that the quirk is applied automatically, thereby
> removing the need for users to modify /etc/modprobe.d/alsa-base (or to
> unload and reload snd-via82xx with ac97_quirk=hp_only).
>
> This patch closes LP#38546.
>
> Signed-off-by: Daniel T Chen <crimsun@xxxxxxxxxx>
> Signed-off-by: Ben Collins <bcollins@xxxxxxxxxx>

Thanks, I applied it to ALSA HG tree, too.


Takashi


> ---
> sound/pci/via82xx.c | 6 ++++++
> 1 files changed, 6 insertions(+)
>
> --- linux-2617-rc6g7.orig/sound/pci/via82xx.c
> +++ linux-2617-rc6g7/sound/pci/via82xx.c
> @@ -1775,6 +1775,12 @@ static struct ac97_quirk ac97_quirks[] =
> .name = "Targa Traveller 811",
> .type = AC97_TUNE_HP_ONLY,
> },
> + {
> + .subvendor = 0x161f,
> + .subdevice = 0x2032,
> + .name = "m680x",
> + .type = AC97_TUNE_HP_ONLY, /* http://launchpad.net/bugs/38546 */
> + },
> { } /* terminator */
> };
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/