mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: Don't cold reset AC97 codecs in some ICH chipsets
Date: Thu, 29 Jan 2009 08:37:53 +0100	[thread overview]
Message-ID: <s5hskn2a7fy.wl%tiwai@suse.de> (raw)
In-Reply-To: <20090128155258.GA4646@vespa.holoscopio.com>

At Wed, 28 Jan 2009 13:52:59 -0200,
Thadeu Lima de Souza Cascardo wrote:
> 
> On Wed, Jan 28, 2009 at 04:20:12PM +0100, Takashi Iwai wrote:
> > At Wed, 28 Jan 2009 12:40:42 -0200,
> > Thadeu Lima de Souza Cascardo wrote:
> > > 
> > > Check in a quirk list if it should do cold reset when AC97 power saving
> > > is enabled. Some devices do not resume properly when cold reset,
> > > although power saving works OK.
> > > 
> > > Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
> > 
> > Thanks, applied now.
> > 
> > ... and soon I found a build error when CONFIG_SND_AC97_POWERSAVE=n.
> > Fixed, too :)
> 
> 
> Sorry for this one. I've cleaned the modules and built them again with a
> changed config. Must have done something wrong in the build. Thanks for
> the fix.
> 
> Regarding the warning fix in 92aab0a0, it is related to this commit:
> 248c982a, which was proposed by you during our previous discussion, and
> didn't really fix my problem.

I can't find these commit ids.  Which tree are you referring to?


thanks,

Takashi

> I've been watching your tree ever since and this patch has been in your
> master branch since then, perhaps awaiting some conclusion about this
> issue.
> 
> Do you think it solves any problems for other device models? In my case,
> if the cold reset was done, this would simply not work.
> 
> Looking closer to the patch now, I see a point in keeping it, which may
> be the reason you did so. It will make the resume faster in those cases
> the init_bits are different from what the driver though would be there.
> 
> In this case, I think the log message should be more clear about that,
> since it seems to indicate that the commit makes the driver wait for
> more codecs (all codec slots) than before the commit.
> 
> Regards,
> Cascardo.

  reply	other threads:[~2009-01-29  7:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 14:40 Thadeu Lima de Souza Cascardo
2009-01-28 15:20 ` Takashi Iwai
2009-01-28 15:52   ` Thadeu Lima de Souza Cascardo
2009-01-29  7:37     ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-28 10:02 Thadeu Lima de Souza Cascardo
2009-01-28 12:06 ` Takashi Iwai
2009-01-28 12:27   ` Thadeu Lima de Souza Cascardo
2009-01-28 13:02     ` 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=s5hskn2a7fy.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=cascardo@holoscopio.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®