linux-kernel - Re: [PATCH 5/5] ACPI: Tie ACPI backlight devices to PCI devices if possible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201102070001.25814.rjw@sisk.pl>
Date:	Mon, 7 Feb 2011 00:01:25 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	akpm@...ux-foundation.org, intel-gfx@...ts.freedesktop.org,
	dri-devel@...ts.freedesktop.org, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org, rpurdie@...ys.net
Subject: Re: [PATCH 5/5] ACPI: Tie ACPI backlight devices to PCI devices if possible

On Sunday, February 06, 2011, Matthew Garrett wrote:
> On Sun, Feb 06, 2011 at 11:41:19PM +0100, Rafael J. Wysocki wrote:
> > On Sunday, February 06, 2011, Matthew Garrett wrote:
> > > Ugh. Ok, how can we fix this?
> > 
> > Not nicely, I'm afraid.
> > 
> > One possible way is to use device_pm_move_after() to rearrange the devices in
> > the PM core's suspend list, but that will happen in the video device being
> > suspended before the new parent (and resumed after it) -- of course, the only
> > option is to move the ACPI video device after the new parent.
> 
> Hang on. Didn't we already have a related issue with the acpi video 
> device being resumed before the video card, resulting in an SMI that 
> hung the system? I thought we'd arranged things such that resuming the 
> ACPI video device wouldn't actually do anything until after the PCI 
> device had been handled? It seems like the correct thing is definitely 
> for it to be suspended before and resumed after...

Yes, it seems so, but I'm not sure what the short term consequences of that
change will be.  Perhaps there will be none. :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/