public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: mark gross <mgross@linux.intel.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-pm@lists.linux-foundation.org"
	<linux-pm@lists.linux-foundation.org>
Subject: Re: Adding PM QoS parameters
Date: Mon, 6 Apr 2009 14:12:37 -0700	[thread overview]
Message-ID: <20090406211237.GA25173@linux.intel.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301CC66C7DE@dbde02.ent.ti.com>

On Fri, Apr 03, 2009 at 01:55:06AM +0530, Premi, Sanjeev wrote:
> I have just started looking at the PM QoS implementation; I came across this
> text in "pm_qos_interface.txt"
> 
> [quote]
> The infrastructure exposes multiple misc device nodes one per implemented
> parameter.  The set of parameters implement is defined by pm_qos_power_init()
> and pm_qos_params.h.  This is done because having the available parameters
> being runtime configurable or changeable from a driver was seen as too easy to
> abuse.
> [/quote]
> 
> Though I have understood the intent; i feel it may also be limiting the use
> where there is a genuine need - specific to an arch/ platform.
> 
> Can we allow number of these params to grow upto a reasonable limit (say 8)?
> If an arch/platform does not specifies more params, everything remains same.
> But we get an opportunity to add arch/platform specific requirements.

If you do this then user mode software using the interface will not be
portable across architectures.  Is that what you want?


What parameters are you looking to add?  I have gotten very little
feedback on what parameters are missing or wanted.

> 
> Not sure if this has already been discussed earlier, but would like to hear
> more thoughts.

This has not been discussed, but changing the data structures to use
handles instead of strings has brought up once without data showing the
strcmps where a measurable issue.

I'm very open to improvements, applications and further discussions.

--mgross


> 
> Best regards,
> Sanjeev
> _______________________________________________
> linux-pm mailing list
> linux-pm@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/linux-pm

  reply	other threads:[~2009-04-06 21:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 20:25 Adding PM QoS parameters Premi, Sanjeev
2009-04-06 21:12 ` mark gross [this message]
2009-04-07  9:00   ` Premi, Sanjeev
2009-04-09 18:57     ` mark gross
2009-04-14 12:24       ` Patrick Bellasi
2009-04-15 18:35         ` mark gross
2009-04-21  8:08           ` Derkling
2009-04-21 23:43             ` mark gross
2009-04-27 12:50               ` Matteo Carnevali
2009-04-27 20:46                 ` mark gross
     [not found] <mailman.459.1240339694.10269.linux-pm@lists.linux-foundation.org>
2009-04-21 20:02 ` Premi, Sanjeev
2009-04-22 16:35   ` mark gross
2009-04-27 12:41   ` Matteo Carnevali
  -- strict thread matches above, loose matches on Subject: below --
2009-04-30 12:28 Patrick Bellasi

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=20090406211237.GA25173@linux.intel.com \
    --to=mgross@linux.intel.com \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=premi@ti.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