All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham-lkml@crca.org.au>
To: Takashi Iwai <tiwai@suse.de>
Cc: Tino Keitel <tino.keitel@gmx.de>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: 2.6.29 regression: left audio channel broken after resume from suspend with Intel HDA
Date: Thu, 07 May 2009 21:54:40 +1000	[thread overview]
Message-ID: <1241697280.19600.203.camel@nigel-laptop> (raw)
In-Reply-To: <s5hy6t92nuz.wl%tiwai@suse.de>

Hi.

On Thu, 2009-05-07 at 12:45 +0200, Takashi Iwai wrote:
> The problem is that BIOS on your machine sets this pin both for
> input and output.  Since it's set as input, the driver respects
> the BIOS setup and skips to override.

'scuse the ignorance, but this makes me ask: Are pins logically
unrelated to jacks? I have a Dell M1530, and it has some jacks that can
work as either inputs or outputs. Under M$, when I plug something in, a
dialog box pops up asking me whether I connected a mic, line in or an
output jack (I forget the details). Sounds like Tino's problem is what
I'd expect from my BIOS. But I'm probably completely ignorant :)

Regards,

Nigel

  reply	other threads:[~2009-05-07 11:54 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 18:40 2.6.29 regression: left audio channel broken after resume from suspend with Intel HDA Tino Keitel
2009-04-20 19:28 ` Rafael J. Wysocki
2009-04-20 19:41 ` Takashi Iwai
2009-04-20 19:41   ` Takashi Iwai
2009-04-20 19:46   ` Tino Keitel
2009-04-21  5:24     ` Takashi Iwai
2009-04-21  5:24       ` Takashi Iwai
2009-04-21  7:32       ` Tino Keitel
2009-04-21  7:39         ` Takashi Iwai
2009-04-21  7:39           ` Takashi Iwai
2009-04-21 18:39           ` Tino Keitel
2009-04-24 14:01             ` Takashi Iwai
2009-04-24 14:21               ` Tino Keitel
2009-04-24 14:41                 ` Takashi Iwai
2009-04-24 14:41                   ` Takashi Iwai
2009-04-28  0:23                   ` Tino Keitel
2009-04-28  5:24                     ` Takashi Iwai
2009-04-28  5:24                       ` Takashi Iwai
2009-04-28  6:30                       ` Tino Keitel
2009-05-06 22:27                     ` Tino Keitel
2009-05-07  7:23                       ` Tino Keitel
2009-05-07  7:40                         ` Justin P. Mattock
2009-05-07  7:40                           ` Justin P. Mattock
2009-05-07 10:07                         ` Takashi Iwai
2009-05-07 10:07                           ` Takashi Iwai
2009-05-07 10:45                         ` Takashi Iwai
2009-05-07 10:45                           ` Takashi Iwai
2009-05-07 11:54                           ` Nigel Cunningham [this message]
2009-05-07 12:16                             ` Takashi Iwai
2009-05-07 12:16                               ` Takashi Iwai
2009-05-07 20:42                               ` Nigel Cunningham
2009-05-07 20:56                                 ` Justin P. Mattock
2009-05-07 20:56                                   ` Justin P. Mattock
2009-05-07 12:59                           ` Tino Keitel
2009-05-08  6:03                             ` Takashi Iwai
2009-05-07 20:42                           ` Tino Keitel
2009-05-07 20:53                             ` Tino Keitel
2009-05-08  6:06                               ` Takashi Iwai
2009-05-08  6:06                                 ` 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=1241697280.19600.203.camel@nigel-laptop \
    --to=ncunningham-lkml@crca.org.au \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tino.keitel@gmx.de \
    --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.