All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.osdl.org
Cc: Matthew Locke <matt@nomadgs.com>,
	patrick.mochel@intel.com, sampsa.fabritius@nokia.com,
	linux@dominikbrodowski.net
Subject: Re: [RFC] PowerOP Take 3, ARM OMAP1 platform support 3/5
Date: Sun, 23 Jul 2006 09:24:50 -0700	[thread overview]
Message-ID: <200607230924.52289.david-b@pacbell.net> (raw)
In-Reply-To: <c55240ed0607201301y7ac3be76o6f173d1b6ab50c1d@mail.gmail.com>

On Thursday 20 July 2006 1:01 pm, Eugeny S. Mints wrote:
> +struct powerop_point {
> +       unsigned int v;         /* voltage in mV */
> +       unsigned int dpll;      /* in KHz */
> +       unsigned int cpu;       /* CPU frequency in KHz */
> +       unsigned int tc;        /* in KHz */
> +       unsigned int per;       /* in KHz */
> +       unsigned int dsp;       /* in KHz */
> +       unsigned int dspmmu;    /* in KHz */
> +       unsigned int lcd;       /* in KHz */
> +};

A few comments:

 - This should be part of patch #4; it's not truly separate.

 - I take it "v" is CPU voltage rather than some random component?
   Either way, there seems to be an omission here since boards
   could have multiple voltages to care about ...

 - In general, shouldn't an operating point be board-specific, so
   that the parts of the system outside the SOC can be included?

 - I'd still rather see operating points be identified by a name
   string of some kind so that the userspace API resembles that
   of /sys/power/state:  just write the state name to that file.

Still looking at the patches, otherwise.

- Dave
  

  reply	other threads:[~2006-07-23 16:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-20 20:01 [RFC] PowerOP Take 3, ARM OMAP1 platform support 3/5 Eugeny S. Mints
2006-07-23 16:24 ` David Brownell [this message]
2006-07-26 21:02   ` Eugeny S. Mints
2006-07-27  0:28     ` David Brownell
2006-07-30 19:32       ` Eugeny S. Mints
2006-07-31  1:58         ` David Brownell
2006-07-31  6:59           ` Vitaly Wool
2006-07-31 21:24             ` David Brownell
2006-08-01 20:52           ` Core PowerOP Interface Update [Was: Re: [RFC] PowerOP Take 3, ARM OMAP1 platform support 3/5] Eugeny S. Mints
2006-08-03  2:07             ` Eugeny S. Mints
2006-08-03 11:26               ` Vitaly Wool
2006-08-03 13:46                 ` Eugeny S. Mints
  -- strict thread matches above, loose matches on Subject: below --
2006-07-27  0:03 [RFC] PowerOP Take 3, ARM OMAP1 platform support 3/5 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=200607230924.52289.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-pm@lists.osdl.org \
    --cc=linux@dominikbrodowski.net \
    --cc=matt@nomadgs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.