All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Paulo Cavalcanti" <promac@gmail.com>,
	"Vedran Miletić" <rivanvx@gmail.com>,
	alsa-devel@alsa-project.org
Subject: Re: idt blue jack patch
Date: Thu, 19 Feb 2009 11:02:12 +0800	[thread overview]
Message-ID: <20090219030212.GA26505@localhost> (raw)
In-Reply-To: <s5hk57nzs1h.wl%tiwai@suse.de>

On Wed, Feb 18, 2009 at 04:24:58PM +0100, Takashi Iwai wrote:
> At Wed, 18 Feb 2009 10:44:26 +0100,
> Vedran Miletić wrote:
> > 
> > On Wed, Feb 18, 2009 at 10:04 AM, Paulo Cavalcanti <promac@gmail.com> wrote:
> > > Takashi,
> > >
> > > Fengguang got the same board I have (DG45ID)
> > > and he confirmed that the blue jack was output.
> > > The only difference between his computer and mine
> > > was that his had an older bios.
> > >
> > > This is what he said to me before sending me the patch:
> > >
> > > "OK, so it's in fact a general issue. I'll look into it. But I'm afraid
> > > I have difficulty in allocating time for it in the near future..."
> > >
> > > Therefore, I think we need another quirk.
> > >
> > > Thanks.
> > >
> > >
> > > --
> > > Paulo Roma Cavalcanti
> > > LCG - UFRJ
> > > _______________________________________________
> > > Alsa-devel mailing list
> > > Alsa-devel@alsa-project.org
> > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> > >

[sorry for being late]

> > 
> > Can you find someone who has different board with same codec to verify
> > how general issue this really is?
>
> In general, the pin config value can't be generic.
> As port-C is a multi-purpose jack, I don't think this can be applied
> to all cases.

I made that hacking patch based on IDT's spec. The value I wrote is in
fact the default value listed in the spec. So it's the Intel BIOS that
changed the default value and make it an output pin.

> So, now the question is when to apply -- under which condition.
> Apparently, the BIOS of Paulo is broken.  And, Wu Fengguang's case
> is unclear, whether it comes from BIOS or from a static pin cfg
> table in patch_sigmatel.c.

After rebooting and force using the generic codec, the 0x0c node still
shows "Pin Default 0x01113014: [Jack] Speaker at Ext Rear". So the
value is from the BIOS.

The only problem is that the pin color is Blue both logically and
physically, which should be input instead of output according to the
convention of color codes.

If you think it's OK, I can refine that patch for submitting.  The
possible regression could be that users connecting speakers to that
pin will find it no longer producing sound after upgrading kernel.

Thanks,
Fengguang

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2009-02-19  3:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16  9:13 idt blue jack patch Paulo Cavalcanti
2009-02-16 10:55 ` Takashi Iwai
2009-02-18  2:04   ` Paulo Cavalcanti
2009-02-18  6:50     ` Takashi Iwai
2009-02-18  9:04       ` Paulo Cavalcanti
2009-02-18  9:44         ` Vedran Miletić
2009-02-18 15:24           ` Takashi Iwai
2009-02-19  3:02             ` Wu Fengguang [this message]
2009-02-19  3:22               ` Tobin Davis
2009-02-19  9:37                 ` Takashi Iwai
2009-02-20  1:00                 ` Wu Fengguang
2009-02-20 10:15                   ` Paulo Cavalcanti
2009-02-20 11:20                     ` Wu Fengguang
2009-02-20 14:16                       ` Paulo Cavalcanti
2009-02-20 14:31                         ` Wu Fengguang
2009-02-20 16:07                           ` Paulo Cavalcanti
2009-02-21  1:05                             ` Wu Fengguang
2009-02-20 17:18                   ` Takashi Iwai
2009-02-21  1:42                     ` Wu Fengguang
2009-02-21 16:28                       ` Takashi Iwai
2009-02-23  8:54                         ` Takashi Iwai
2009-02-23  9:53                           ` Wu Fengguang
2009-02-23 10:21                             ` Takashi Iwai
2009-02-23 12:58                               ` Wu Fengguang
2009-02-23 13:00                                 ` Takashi Iwai
2009-02-23 16:15                                   ` Takashi Iwai
2009-02-24  2:30                                     ` Wu Fengguang
2009-02-21  1:55                     ` Wu Fengguang
2009-02-21  2:42                       ` Paulo Cavalcanti
2009-02-21  2:56                         ` Wu Fengguang
2009-02-21  3:12                           ` Paulo Cavalcanti
2009-02-21 16:28                       ` Takashi Iwai

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=20090219030212.GA26505@localhost \
    --to=fengguang.wu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=promac@gmail.com \
    --cc=rivanvx@gmail.com \
    --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.