From: Sudeep K N <sudeepholla.maillist@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@sisk.pl, devicetree-discuss@lists.ozlabs.org,
spear-devel@list.st.com, cpufreq@vger.kernel.org,
Deepak Sikri <deepak.sikri@st.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] cpufreq: SPEAr: Add CPUFreq driver
Date: Tue, 27 Nov 2012 09:24:55 +0000 [thread overview]
Message-ID: <CAPKp9uZ-HpAp2KO9qKXsMCoGJS3Vn-VW34h6cbv8o01Vzzi4jw@mail.gmail.com> (raw)
In-Reply-To: <7ec0e3f4b81b70f3def4257e6b9781efd4c7a3d2.1353785862.git.viresh.kumar@linaro.org>
On Sat, Nov 24, 2012 at 7:39 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
[...]
> diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-spear.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-spear.txt
> new file mode 100644
> index 0000000..4cf2819
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-spear.txt
> @@ -0,0 +1,29 @@
> +SPEAr cpufreq driver
> +-------------------
> +
> +SPEAr SoC cpufreq driver for CPU frequency scaling.
> +It supports both uniprocessor (UP) and symmetric multiprocessor (SMP) systems
> +which share clock across all CPUs.
If this is the case, is there any particular reason why you cannot use
the generic
cpufreq-cpu0 driver ?
Regards,
Sudeep
next prev parent reply other threads:[~2012-11-27 9:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 19:39 [PATCH] cpufreq: SPEAr: Add CPUFreq driver Viresh Kumar
2012-11-24 20:45 ` Rafael J. Wysocki
2012-11-27 4:01 ` Shawn Guo
2012-11-27 3:58 ` Viresh Kumar
2012-11-27 4:16 ` Deepak Sikri
2012-11-27 5:16 ` Shawn Guo
2012-11-27 4:53 ` Viresh Kumar
2012-11-27 11:38 ` Rafael J. Wysocki
2012-11-27 11:35 ` Viresh Kumar
2012-11-27 12:06 ` Rafael J. Wysocki
2012-11-27 9:24 ` Sudeep K N [this message]
2012-11-27 9:33 ` Viresh Kumar
2012-11-27 11:19 ` Sudeep K N
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=CAPKp9uZ-HpAp2KO9qKXsMCoGJS3Vn-VW34h6cbv8o01Vzzi4jw@mail.gmail.com \
--to=sudeepholla.maillist@gmail.com \
--cc=cpufreq@vger.kernel.org \
--cc=deepak.sikri@st.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rjw@sisk.pl \
--cc=spear-devel@list.st.com \
--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;
as well as URLs for NNTP newsgroup(s).