From: Pavel Machek <pavel@ucw.cz>
To: "Gross, Mark" <mark.gross@intel.com>
Cc: "Mochel, Patrick" <patrick.mochel@intel.com>,
linux-pm@lists.osdl.org, sampsa.fabritius@nokia.com,
linux@dominikbrodowski.net
Subject: Re: [RFC] PowerOP Take 3, sysfs UI core 2/5
Date: Sat, 5 Aug 2006 12:05:04 +0000 [thread overview]
Message-ID: <20060805120504.GA5417@ucw.cz> (raw)
In-Reply-To: <5389061B65D50446B1783B97DFDB392D01F607DB@orsmsx411.amr.corp.intel.com>
Hi!
> >> Please note that the interface is not hooked up with the rest of the
> code
> >> yet and is provided just for reference/review.
>
> Drivers/powerop/powerop_sysfs.c : includes asm/powerop.h and will not
> compile on i386.
> There are other places where it will not compile for non-omap
> architectures. The architecture independent code should build for all
> architectures.
>
> Now just rambling a bit, while catching up on the email thread some of
> this may be wrong but....
>
> Is it realistic to have the dimensionality of the operating points
> defined at the architecture level? Why couldn't there be multiple types
> of operating points based on presence of different peripherals? Having
> the array defined at compile time seems wrong. Couldn't the platform
It is complex enough already, please don't overdesign it even more.
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-08-05 12:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 23:55 [RFC] PowerOP Take 3, sysfs UI core 2/5 Gross, Mark
2006-08-01 11:16 ` Matthew Locke
2006-08-05 12:05 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-27 0:30 Gross, Mark
2006-07-27 0:15 Gross, Mark
2006-07-27 0:14 Gross, Mark
2006-07-20 19:56 Eugeny S. Mints
2006-07-20 20:00 ` Eugeny S. Mints
2006-07-24 17:29 ` Pavel Machek
2006-07-24 18:48 ` David Brownell
2006-07-24 19:35 ` Pavel Machek
2006-07-24 19:40 ` Matthew Locke
2006-07-24 21:46 ` David Brownell
2006-07-24 21:58 ` Preece Scott-PREECE
2006-07-25 0:32 ` David Brownell
2006-07-25 10:09 ` Amit Kucheria
2006-07-26 5:05 ` David Brownell
2006-07-26 7:24 ` Matthew Locke
2006-08-05 12:09 ` Pavel Machek
2006-08-07 4:31 ` Vitaly Wool
2006-07-26 21:11 ` Eugeny S. Mints
2006-07-27 0:58 ` David Brownell
2006-07-26 7:44 ` Matthew Locke
2006-07-26 15:03 ` Christian Krafft
2006-07-27 0:55 ` David Brownell
2006-08-01 10:45 ` Matthew Locke
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=20060805120504.GA5417@ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-pm@lists.osdl.org \
--cc=linux@dominikbrodowski.net \
--cc=mark.gross@intel.com \
--cc=patrick.mochel@intel.com \
--cc=sampsa.fabritius@nokia.com \
/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