From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robherring2@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] cpufreq: enable ARM drivers on arm64
Date: Thu, 5 Dec 2013 18:16:06 +0000 [thread overview]
Message-ID: <20131205181606.GY29268@sirena.org.uk> (raw)
In-Reply-To: <1386202994-30784-2-git-send-email-robherring2@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 559 bytes --]
On Wed, Dec 04, 2013 at 06:23:13PM -0600, Rob Herring wrote:
> From: Rob Herring <rob.herring@calxeda.com>
>
> Enable cpufreq and power kconfig menus on arm64 along with arm cpufreq
> drivers. The power menu is needed for OPP support. At least on Calxeda
> systems, the same cpufreq driver is used for arm and arm64 based
> systems.
If this needs any revisions (I'd be surprised but...) can you please
keep me on the CCs? I intend to pull this into LSK if that's OK since I
was about to do roughly the same thing for it and upstream the result.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2013-12-05 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 0:23 [PATCH 0/2] Enable Calxeda cpufreq driver on arm64 Rob Herring
2013-12-05 0:23 ` [PATCH 1/2] cpufreq: enable ARM drivers " Rob Herring
2013-12-05 18:16 ` Mark Brown [this message]
2013-12-05 20:03 ` Rob Herring
2013-12-05 20:35 ` Mark Brown
2013-12-05 0:23 ` [PATCH 2/2] cpufreq: highbank: rework the kconfig dependencies for arm64 Rob Herring
2013-12-16 8:54 ` Viresh Kumar
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=20131205181606.GY29268@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
--cc=viresh.kumar@linaro.org \
--cc=will.deacon@arm.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