From: David Henningsson <david.henningsson@canonical.com>
To: Anisse Astier <anisse@astier.eu>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: hda : computer using EAPD as external amplifier controller
Date: Thu, 20 Jan 2011 10:07:55 +0100 [thread overview]
Message-ID: <4D37FB6B.9040701@canonical.com> (raw)
In-Reply-To: <20110119182448.2c8dbf28@destiny.ordissimo>
On 2011-01-19 18:24, Anisse Astier wrote:
> Hi,
>
> I have this computer, with an integrated speaker. It's using an ALC662,
> see attached alsa-info output.
>
> By default, speaker doesn't work. Now, after playing a bit with
> hda-analyzer, I figured that output PIN 0x14 has EAPD enabled, which is
> the default way of doing things in auto configure mode. But disabling
> EAPD on this PIN makes speaker work. See second alsa-info attached.
>
> Is it necessary to write a full blown quirk just to modify this parameter?
>
> From what I've seen in patch_realtek, it seems we need to write the whole
> config for the device when adding a quirk: we can't rely on auto
> configuration and then put a small quirk on top of that. Am I right ?
Perhaps this commit can give you some inspiration?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=357f915ece53aa4c8759087888346145848ea753
...although Takashi just rewrote the quirking system a bit, so you'll
have to adjust to that when you add your (similar) quirk.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2011-01-20 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 17:24 hda : computer using EAPD as external amplifier controller Anisse Astier
2011-01-20 9:07 ` David Henningsson [this message]
2011-01-20 9:42 ` Takashi Iwai
2011-01-20 11:36 ` [PATCH] ALSA: hda - Fix EAPD to low on CZC P10T tablet computer with ALC662 Anisse Astier
2011-01-20 12:00 ` Takashi Iwai
2011-01-20 10:00 ` hda : computer using EAPD as external amplifier controller Anisse Astier
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=4D37FB6B.9040701@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=anisse@astier.eu \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.