From: "Eugeny S. Mints" <eugeny.mints@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: pm list <linux-pm@lists.osdl.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [PATCH] PowerOP, PowerOP Core, 1/2
Date: Mon, 18 Sep 2006 15:32:44 +0400 [thread overview]
Message-ID: <450E83DC.4050503@gmail.com> (raw)
In-Reply-To: <20060918104437.GA4973@elf.ucw.cz>
Pavel Machek wrote:
> Hi!
>
>> The PowerOP Core provides completely arch independent interface
>> to create and control operating points which consist of arbitrary
>> subset of power parameters available on a certain platform.
>> Also, PowerOP Core provides optional SysFS interface to access
>> operating point from userspace.
>
> Please inline patches and sign them off.
hmm, seems my bad. will double check.
>
> Also if you are providing new userland interface, describe it... in
> Documentation/ABI.
seems already discussed
>> +struct powerop_driver {
>> + char *name;
>> + void *(*create_point) (const char *pwr_params, va_list args);
>> + int (*set_point) (void *md_opt);
>> + int (*get_point) (void *md_opt, const char *pwr_params, va_list args);
>> +};
>
> We can certainly get better interface than va_list, right?
Please elaborate.
>
>> +
>> +#
>> +# powerop
>> +#
>> +
>> +menu "PowerOP (Power Management)"
>> +
>> +config POWEROP
>> + tristate "PowerOP Core"
>> + help
>
> Hohum, this is certainly going to be clear to confused user...
please elaborate.
>> + list_add_tail(&opt->node, &named_opt_list);
>> + strcpy(registered_names[registered_opt_number], id);
>> + registered_opt_number++;
>> + up(&named_opt_list_mutex);
>> +
>> + blocking_notifier_call_chain(&powerop_notifier_list,
>> + POWEROP_REGISTER_EVENT, id);
>> + return 0;
>> +
>> + fail_set_name:
>> + kfree(opt->md_opt);
>> +
>> + fail_opt_create:
>> + kfree(registered_names[registered_opt_number]);
>> +
>> + fail_name_nomem:
>> + kfree(opt);
>> + return err;
>> +}
>
> Careful about spaces vs. tabs...
will double check but I'm pretty sure I ran all files thru lindent.
> ...so, you got support for 20 operating points... And this should
> include devices, too, right?
sorry, don't understand the question. an operating point is a set of platform
power parameters.
>How is it going to work on 8cpu box? will
> you have states like cpu1_800MHz_cpu2_1600MHz_cpu3_800MHz_... ?
i do not operate with term 'state' so I don't understand what it means here.
Eugeny
> Pavel
next prev parent reply other threads:[~2006-09-18 11:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 14:37 [PATCH] PowerOP, PowerOP Core, 1/2 Eugeny S. Mints
2006-09-18 10:44 ` [linux-pm] " Pavel Machek
2006-09-18 11:32 ` Eugeny S. Mints [this message]
2006-09-18 19:58 ` Eugeny S. Mints
2006-09-18 20:07 ` Vitaly Wool
2006-09-19 18:22 ` Pavel Machek
2006-09-18 13:23 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2006-09-19 19:46 [linux-pm] " Scott E. Preece
2006-09-19 20:06 ` Eugeny S. Mints
2006-09-22 14:09 ` Pavel Machek
2006-09-26 21:45 ` Matthew Locke
2006-09-19 21:37 Scott E. Preece
2006-09-22 14:11 ` Pavel Machek
2006-09-22 14:48 ` Igor Stoppa
2006-09-22 20:28 Scott E. Preece
2006-09-22 21:18 ` Vitaly Wool
2006-09-22 20:34 Scott E. Preece
2006-09-23 11:18 ` Pavel Machek
2006-09-24 21:33 ` Matthew Locke
2006-09-24 21:45 ` Pavel Machek
2006-09-22 21:10 Woodruff, Richard
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=450E83DC.4050503@gmail.com \
--to=eugeny.mints@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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