From: David Brown <davidb@quicinc.com>
To: mark gross <mgross@linux.intel.com>
Cc: Daniel Walker <dwalker@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Brown, David" <davidb@quicinc.com>,
"Chidambaram, Praveen" <pchidamb@quicinc.com>
Subject: Re: [PATCH] pm_qos: Add QoS param, minimum system bus frequency
Date: Mon, 4 Jan 2010 15:18:52 -0800 [thread overview]
Message-ID: <20100104231852.GA29950@huya.qualcomm.com> (raw)
In-Reply-To: <20100104213852.GA5031@linux.intel.com>
On Mon, Jan 04, 2010 at 01:38:52PM -0800, mark gross wrote:
> 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.)
We're part of a system with several other devices. Our driver
just passes the frequency on as our voted minimum.
Look for PM_QOS_SYSTEM_BUS_FREQ in the file:
https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=blob;f=arch/arm/mach-msm/clock.c;h=3a22b5abb8e8acf876367dc6c013fe507af9c0ac;hb=287d333b03df8faafd3a480abc8e121110870839
http://tinyurl.com/ye7eg33
David
next prev parent reply other threads:[~2010-01-04 23:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 1:20 Daniel Walker
2010-01-01 1:22 ` Daniel Walker
2010-01-04 21:38 ` mark gross
2010-01-04 22:00 ` Daniel Walker
2010-01-06 18:39 ` mark gross
2010-01-04 23:18 ` David Brown [this message]
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=20100104231852.GA29950@huya.qualcomm.com \
--to=davidb@quicinc.com \
--cc=dwalker@codeaurora.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome