mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Starvik <mikael.starvik@axis.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	David Miller <davem@davemloft.net>,
	Eric Miao <eric.y.miao@gmail.com>,
	Jesper Nilsson <jespern@axis.com>,
	John Crispin <blogic@openwrt.org>,
	linux-cris-kernel <linux-cris-kernel@axis.com>,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
	Paul Mundt <lethal@linux-sh.org>, Sekhar Nori <nsekhar@ti.com>,
	"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
	Miao Steven <realmz6@gmail.com>, Dave Jones <davej@redhat.com>
Subject: Re: [Query] CPUFreq: Does these machines have separate clock domains for CPUs?
Date: Fri, 30 Aug 2013 06:21:19 +0200	[thread overview]
Message-ID: <D9E0917B-058A-4F22-87EF-15F26ED46F35@axis.com> (raw)
In-Reply-To: <CAKohponWn-RN7-6sdhghd6RGCOd357G+TKLsxHfqnSCuMD7xxw@mail.gmail.com>

Cris are also UP

29 aug 2013 kl. 12:16 skrev "Viresh Kumar" <viresh.kumar@linaro.org>:

> Hi,
> 
> I have been doing some CPUFreq cleanup work and
> wanted to know if the below mentioned machines have separate
> clock domains for their CPUs or all share the same domain?
> 
> So, that we can use some generic routines for these drivers which
> would eventually do:
> 
> cpumask_setall(policy->cpus);
> 
> And I wanted to make sure that this doesn't break them.. :)
> 
> ......
> 
> The drivers are:
> 
> drivers/cpufreq/at32ap-cpufreq.c
> drivers/cpufreq/blackfin-cpufreq.c
> drivers/cpufreq/cris-artpec3-cpufreq.c
> drivers/cpufreq/cris-etraxfs-cpufreq.c
> drivers/cpufreq/davinci-cpufreq.c
> drivers/cpufreq/e_powersaver.c
> drivers/cpufreq/elanfreq.c
> drivers/cpufreq/longhaul.c
> drivers/cpufreq/loongson2_cpufreq.c
> drivers/cpufreq/pmac32-cpufreq.c
> drivers/cpufreq/powernow-k6.c
> drivers/cpufreq/powernow-k7.c
> drivers/cpufreq/pxa2xx-cpufreq.c
> drivers/cpufreq/pxa3xx-cpufreq.c
> drivers/cpufreq/sc520_freq.c
> drivers/cpufreq/sh-cpufreq.c
> drivers/cpufreq/sparc-us2e-cpufreq.c
> drivers/cpufreq/sparc-us3-cpufreq.c
> 
> --
> Viresh

  parent reply	other threads:[~2013-08-30  4:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 10:15 Viresh Kumar
2013-08-29 10:23 ` Sekhar Nori
2013-08-29 10:30   ` Viresh Kumar
2013-08-29 10:27     ` Sekhar Nori
2013-08-29 10:33       ` Viresh Kumar
2013-08-29 22:41 ` Aaro Koskinen
2013-08-30  4:21 ` Mikael Starvik [this message]
2013-08-30  6:48 ` Magnus Damm
2013-08-30  7:33   ` Viresh Kumar
2013-09-04  7:27     ` Magnus Damm
2013-08-30  8:49 ` Benjamin Herrenschmidt

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=D9E0917B-058A-4F22-87EF-15F26ED46F35@axis.com \
    --to=mikael.starvik@axis.com \
    --cc=benh@kernel.crashing.org \
    --cc=blogic@openwrt.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=eric.y.miao@gmail.com \
    --cc=jespern@axis.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=realmz6@gmail.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=viresh.kumar@linaro.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

all inboxes | Powered by JetHome®