| 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
| ||
|
Message-ID: <20080118014254.GA14818@srcf.ucam.org> Date: Fri, 18 Jan 2008 01:42:54 +0000 From: Matthew Garrett <mjg59@...f.ucam.org> To: Zhang Rui <rui.zhang@...el.com> Cc: lenb@...nel.org, linux-acpi@...r.kernel.org, linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, "Thomas, Sujith" <sujith.thomas@...el.com> Subject: Re: [PATCH 6/10] ACPI: register ACPI Video LCD as generic thermal cooling device On Fri, Jan 18, 2008 at 09:31:40AM +0800, Zhang Rui wrote: > Just like I don't think lcd should be used for ACPI thermal management > before I saw it is listed in _TZD and intel_menlow requires to throttle > it when overheating, why not let the individual drivers implement the > callbacks if there is clearly a request to do this. > And we can add this to the generic acpi_device struct then if this is a > common feature for all ACPI devices. It'll probably never be common for all ACPI devices, but it's already required for three types. I think that's a strong argument for making it generic. > Well, you're right. > But in order to throttle the lcd, this is reasonable, right? Moving the common code into its own routine and then calling that from each of the others would probably work. -- Matthew Garrett | mjg59@...f.ucam.org -- 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/
Powered by blists - more mailing lists