If they're defined dynamically, you can change them without recompiling the system, building a new rootfs image, etc. This is especially useful during development and tuning of systems built on new hardware, since the set of Ops available (that is, that are documented by the chip vendor to work) can vary over time and even board-to-board. scott -----Original Message----- From: linux-pm-bounces at lists.osdl.org [mailto:linux-pm-bounces at lists.osdl.org] On Behalf Of David Brownell Sent: Monday, July 24, 2006 4:47 PM To: linux-pm at lists.osdl.org Cc: Matthew Locke; patrick.mochel at intel.com; linux at dominikbrodowski.net; sampsa.fabritius at nokia.com; Pavel Machek Subject: Re: [linux-pm] [RFC] PowerOP Take 3, sysfs UI core 2/5 On Monday 24 July 2006 12:35 pm, Pavel Machek wrote: > > > > But better run this by lkml. > > > > I'd rather see some rough consensus on this list that this is the > > right way to head, before running things like this by LKML. > > I meant "they could suggest how to do the sysfs thing, in reasonable > way". Like echo new_config > file is extermely ugly, but perhaps > configfs is suitable? Makes some sense. But I'm still puzzled why _creating_ an operating point would be done outside of the arch/.../board-xx.c file. - Dave _______________________________________________ linux-pm mailing list linux-pm at lists.osdl.org https://lists.osdl.org/mailman/listinfo/linux-pm
