From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.osdl.org
Cc: Matthew Locke <matt@nomadgs.com>,
Preece Scott-PREECE <scott.preece@motorola.com>
Subject: Re: [RFC] PowerOP Take 3, sysfs UI core 2/5
Date: Tue, 25 Jul 2006 22:05:35 -0700 [thread overview]
Message-ID: <200607252205.37086.david-b@pacbell.net> (raw)
In-Reply-To: <1153822154.5875.16.camel@localhost>
On Tuesday 25 July 2006 3:09 am, Amit Kucheria wrote:
> On Mon, 2006-07-24 at 17:32 -0700, ext David Brownell wrote:
> > On Monday 24 July 2006 2:58 pm, Preece Scott-PREECE wrote:
> > > 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.
> >
> > I could easily buy such a mechanism being dependent on EXPERIMENTAL,
> > for use with developer/prototype boards ... thanks for that scenario.
> >
> > But I have a harder time seeing it used in production systems, burnt
> > into flash on a manufacturing line that already had to qualify that
> > new hardware before the next production run (of say 10,000 units) was
> > approved by the powers-that-be.
> >
> > - Dave
>
> Sometimes a certain operating point is not desired for regular operation
> of the device. So it would not be in the board-xx.c file.
>
> But connect a peripheral and suddenly this is the most attractive OP for
> the system.
And you'd know that in advance, and thus could predefine that OP. :)
Even in the worst case, where you somehow add a driver without
upgrading the rest of the kernel in flash, that driver should be
able to define an OP without userspace. (I suppose there are some
product vendors willing to do that type of field upgrade.)
I'm still not persuaded that a UI for OP creation is needed except
for development. Feel free to keep trying to persuade me though;
I'm just pushing back on what I see as weak points, since that's
the best way I know to come up with good solutions.
- Dave
> So the ability to add operating points from userspace might
> be helpful there.
>
> Regards,
> Amit
>
> >
> > > > 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.
> > _______________________________________________
> > linux-pm mailing list
> > linux-pm@lists.osdl.org
> > https://lists.osdl.org/mailman/listinfo/linux-pm
> --
> Amit Kucheria <amit.kucheria@nokia.com>
> Nokia
> _______________________________________________
> linux-pm mailing list
> linux-pm@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/linux-pm
>
next prev parent reply other threads:[~2006-07-26 5:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 19:56 [RFC] PowerOP Take 3, sysfs UI core 2/5 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 23:55 Gross, Mark
2006-08-01 11:16 ` Matthew Locke
2006-08-05 12:05 ` Pavel Machek
2006-07-27 0:14 Gross, Mark
2006-07-27 0:15 Gross, Mark
2006-07-27 0:30 Gross, Mark
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=200607252205.37086.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-pm@lists.osdl.org \
--cc=matt@nomadgs.com \
--cc=scott.preece@motorola.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