All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@codeaurora.org>
To: mgross@linux.intel.com
Cc: linux-kernel@vger.kernel.org, davidb@quicinc.com, pchidamb@quicinc.com
Subject: Re: [PATCH] pm_qos: Add QoS param, minimum system bus frequency
Date: Mon, 04 Jan 2010 14:00:45 -0800	[thread overview]
Message-ID: <1262642445.3097.11.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100104213852.GA5031@linux.intel.com>

On Mon, 2010-01-04 at 13:38 -0800, mark gross wrote:
> On Thu, Dec 31, 2009 at 05:20:27PM -0800, Daniel Walker wrote:
> > From: Praveen Chidambaram <pchidamb@quicinc.com>
> > 
> > In some systems, the system bus speed can be varied, usually
> > based on the current CPU frequency.  However, various device
> > drivers and/or applications may need a faster system bus for I/O
> > even though the CPU itself may be idle
> 
> What happened to the discussion around multiple platforms needing
> multiple bus pm_qos_requirements?  
> 
> Is system bus freq too generic? (I'm worried about the name space)
> Is this ok? (I'm asking linux-pm for input here.)
> On X86 would this be analogous to FSB, Memory, or PCI bus frequencies?
> What will happen when there are two buses each wanting a PM_QOS
> parameter?  Is that a likely scenario?

We can always change the naming in the future, but someone could add a
PM_QOS_MEMORY_BUS_FREQ or PM_QOS_PERIPHERAL_BUS_FREQ in addition to this
one.. Since it's all generic code having generic naming seems fine..

> Also, on your platform you have a throttling driver controlling the
> frequency of some bus, that will use this value as a constraint on how
> far it will throttle.  no?  I would be interested in seeing this driver
> sometime.  (I just want to make sure no one bastardizes pm_qos into an
> operating point thing.  I'm not sure I can justify why but I want to
> avoid that.)

When you say "operating point thing" do you mean you don't want the
frequency adjusted at runtime? You want it set once then move on?

Daniel


  reply	other threads:[~2010-01-04 22:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-01  1:20 [PATCH] pm_qos: Add QoS param, minimum system bus frequency Daniel Walker
2010-01-01  1:22 ` Daniel Walker
2010-01-04 21:38 ` mark gross
2010-01-04 22:00   ` Daniel Walker [this message]
2010-01-06 18:39     ` mark gross
2010-01-04 23:18   ` David Brown
2010-01-06 18:49     ` mark gross
2010-01-04 23:22   ` Chidambaram, Praveen
2010-01-06 18:56     ` mark gross
2010-01-07 16:34 ` Kevin Hilman
2010-01-07 20:52   ` mark gross
2010-01-07 22:28     ` Kevin Hilman
2010-01-08 18:59   ` Daniel Walker

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=1262642445.3097.11.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --cc=davidb@quicinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=pchidamb@quicinc.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.