From: Scott Wood <scottwood@freescale.com>
To: Zhao Chenhui <chenhui.zhao@freescale.com>
Cc: Jerry Huang <Chang-Ming.Huang@freescale.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 4/7] powerpc/85xx: add support to JOG feature using cpufreq interface
Date: Wed, 9 Nov 2011 10:13:31 -0600 [thread overview]
Message-ID: <20111109161331.GA7950@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <20111109113813.GB3303@localhost.localdomain>
On Wed, Nov 09, 2011 at 07:38:13PM +0800, Zhao Chenhui wrote:
> On Mon, Nov 07, 2011 at 12:50:24PM -0600, Scott Wood wrote:
> > On 11/07/2011 04:27 AM, Zhao Chenhui wrote:
> > > There is only one ppc_proc_freq. no lock.
> >
> > I realize there's only one.
> >
> > I'm asking whether CPUs can have their frequencies set indpendently --
> > if the answer is no, and this function is not specific to a CPU, my only
> > concern is the lock. Either this function can be called multiple times
> > in parallel, in which case the ppc_proc_freq update should be inside the
> > lock, or it can't, in which case why do we need the lock at all?
> >
> > -Scott
>
> Yes. They can be changed independently.
> I will set ppc_proc_freq inside the lock.
If they can be changed independently, what does the global ppc_proc_freq
mean?
-Scott
next prev parent reply other threads:[~2011-11-09 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 12:36 [PATCH 4/7] powerpc/85xx: add support to JOG feature using cpufreq interface Zhao Chenhui
2011-11-04 19:42 ` Scott Wood
2011-11-07 10:27 ` Zhao Chenhui
2011-11-07 18:50 ` Scott Wood
2011-11-09 11:38 ` Zhao Chenhui
2011-11-09 16:13 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-03 12:34 [PATCH 1/7] powerpc/85xx: re-enable timebase sync disabled by KEXEC patch Li Yang
2010-12-03 12:34 ` [PATCH 2/7] powerpc/85xx: add HOTPLUG_CPU support Li Yang
2010-12-03 12:34 ` [PATCH 3/7] powerpc/85xx: add the deep sleep support Li Yang
2010-12-03 12:34 ` [PATCH 4/7] powerpc/85xx: add support to JOG feature using cpufreq interface Li Yang
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=20111109161331.GA7950@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=Chang-Ming.Huang@freescale.com \
--cc=chenhui.zhao@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).