Re: [RFC][PATCH 2/2] ACPI PM: Add possibility to change suspend sequence

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday, 12 of May 2008, Pavel Machek wrote:
> Hi!
> 
> > Index: linux-2.6/Documentation/kernel-parameters.txt
> > ===================================================================
> > --- linux-2.6.orig/Documentation/kernel-parameters.txt
> > +++ linux-2.6/Documentation/kernel-parameters.txt
> > @@ -157,6 +157,11 @@ and is between 256 and 4096 characters. 
> >  			default: The hardware signature is checked during
> >  			         resume from S4.
> >  
> > +	acpi_old_suspend_ordering [HW,ACPI] ACPI suspend ordering
> > +			Enforce the ACPI 1.0 ordering of the _PTS control
> > +			method wrt putting devices into low power states
> > +			default: ACPI 2.0 ordering of _PTS
> > +
> >  	acpi_sci=	[HW,ACPI] ACPI System Control Interrupt trigger mode
> >  			Format: { level | edge | high | low }
> >
> 
> Hmm, I have a wild idea...
> 
> acpi_sleep=old_ordering
> 
> ...and reuse the same variable we already use for
> s3_bios/s3_mode. Then, we'd be able to blacklist the systems needing
> old_ordering from s2ram...
> 
> I guess this whitelist should better be done in kernel, but short-term
> ability to whitelist from userland could not hurt...?

There's one problem with that, acpi_sleep is x86-specific and it's actually
handled in arch/x86/kernel/acpi/sleep.c .  Well, ok, I think I can handle that,
but it won't look nice.

Thanks,
Rafael
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm

[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux