Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Matt Mullins <mokomull@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Fwd: Problems with hda_intel, Santa Rosa, and suspend
Date: Wed, 27 Jun 2007 14:42:57 +0200	[thread overview]
Message-ID: <s5hsl8deffy.wl%tiwai@suse.de> (raw)
In-Reply-To: <dfd4051f0706251316uf265b3dw9c069dc5f75ceedf@mail.gmail.com>

At Mon, 25 Jun 2007 15:16:41 -0500,
Matt Mullins wrote:
> 
> On 6/25/07, Takashi Iwai <tiwai@suse.de> wrote:
> > > Yes, single_cmd mode is used always.
> > That's bad.
> 
> I believe we have established that.  What can I do about it?  *Can* I
> do anything about it?  What functions should I start debugging?  Has
> this happened with other codecs before?  What documentation will I
> need or want other than the Intel HDA and STAC9205 specifications?

Similar problems have been seen in some laptops, too.  I vaguely
remember that they need some ACPI-related boot options to fix it
somehow.  I think it's likely irrelevant with the codec chip, but
rather a problem of the controller side.

> I'm definitely willing to help work on this, as not many people have
> this hardware.  I'm just new to the sound system, so I'm still trying
> to figure out what-calls-what.


Takashi

  parent reply	other threads:[~2007-06-27 12:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dfd4051f0706161836xa191176ke10deff2868ad8d6@mail.gmail.com>
     [not found] ` <200706171149.27547.rjw@sisk.pl>
     [not found]   ` <dfd4051f0706171355i7bc3d4b7qe9aee2acb904c8c@mail.gmail.com>
2007-06-18  0:35     ` Fwd: Problems with hda_intel, Santa Rosa, and suspend Matt Mullins
2007-06-18  0:49       ` Lee Revell
2007-06-18  1:59         ` Matt Mullins
2007-06-19 10:56           ` Takashi Iwai
     [not found]             ` <dfd4051f0706191354i679c5b82pd8d788dfb012df3d@mail.gmail.com>
2007-06-20 10:14               ` Takashi Iwai
2007-06-20 21:18                 ` Matt Mullins
2007-06-21 10:29                   ` Takashi Iwai
2007-06-22 20:31                     ` Matt Mullins
2007-06-25 10:18                       ` Takashi Iwai
     [not found]                         ` <dfd4051f0706251316uf265b3dw9c069dc5f75ceedf@mail.gmail.com>
2007-06-25 20:17                           ` Fwd: " Matt Mullins
2007-06-27 12:42                           ` Takashi Iwai [this message]
2007-07-04 20:37                             ` Matt Mullins
2007-07-05 11:03                               ` Takashi Iwai
2007-07-05 22:13                                 ` Matt Mullins
2007-07-06  2:42                                   ` Matt Mullins
2007-07-06  9:32                                     ` Takashi Iwai
2007-07-06 15:46                                       ` Thorsten Leemhuis
2007-07-06 16:19                                         ` Takashi Iwai
2007-07-06 16:56                                           ` Thorsten Leemhuis
2007-07-09 12:52                                             ` Takashi Iwai
2007-07-09 15:09                                               ` Thorsten Leemhuis
2007-06-29  6:13 albox
2007-06-29 23:00 ` 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=s5hsl8deffy.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=mokomull@gmail.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