From: Takashi Iwai <tiwai@suse.de>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
alsa-devel@alsa-project.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] [PATCH] snd-es1968: remove pm_whitelist
Date: Sun, 04 Nov 2012 09:29:25 +0100 [thread overview]
Message-ID: <s5h7gq1srdm.wl%tiwai@suse.de> (raw)
In-Reply-To: <201211012258.31310.linux@rainbow-software.org>
At Thu, 1 Nov 2012 22:58:30 +0100,
Ondrej Zary wrote:
>
> On Thursday 01 November 2012 22:29:43 Alan Cox wrote:
> > On Thu, 1 Nov 2012 21:55:54 +0100
> >
> > Ondrej Zary <linux@rainbow-software.org> wrote:
> > > pm_whitelist breaks suspend on all non-whitelisted cards for unknown
> > > purpose. Remove it. This fixes suspend on Terratec DMX and SF64-PCE2
> > > cards.
> >
> > Because lots of them broke laptops.
> >
> > Why not just whitelist the ones you know works, given there are ones we
> > know doesn't so your patch is an instant regression guarantee ?
> >
> > (and yes a blacklist might have been brighter but I don't know the
> > history and it's a bit late to fix)
>
> I wonder what does the suspend/resume code break? Currently, all
> non-whitelisted cards are broken (not working after resume).
You can't expect anything logical with the broken ACPI support on such
old hardware :)
> The problem with adding cards to the whitelist is that Terratec DMX has
> generic subsystem ID:
> ESS Technology ES1978 Maestro 2E [125d:1978] (rev 10)
> Subsystem: ESS Technology ES1978 Maestro 2E [125d:1978]
>
> Adding this to the whitelist does not look like a good idea...
But better than possibly breaking all units without testing.
The fact that the device contains only the ES1978 SSID implies that
it's a PCI sound card, not an on-board device. Thus the possibility
to regress for such a case is fairly low. The concern is basically
only for the onboard sound devices on old laptops.
thanks,
Takashi
prev parent reply other threads:[~2012-11-04 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 20:55 Ondrej Zary
2012-11-01 21:29 ` Alan Cox
2012-11-01 21:58 ` Ondrej Zary
2012-11-04 8:29 ` Takashi Iwai [this message]
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=s5h7gq1srdm.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.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®