From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH 1/2] cpufreq: enable ARM drivers on arm64
Date: Thu, 5 Dec 2013 20:35:19 +0000 [thread overview]
Message-ID: <20131205203519.GA29268@sirena.org.uk> (raw)
In-Reply-To: <52A0DC28.1040001@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On Thu, Dec 05, 2013 at 02:03:52PM -0600, Rob Herring wrote:
> Will do, but I'm surprised we're at the point on arm64 of needing LSK.
ARMv8 isn't just for servers, and of course there's the desire to have
the software as ready as early as it can be!
> There's a couple of subsystems that need enabling. I've posted EDAC
> patches (need to send v3). cpuidle is another. Probably some more I
> haven't looked at.
Right, cpuidle is in progress - Lorenzo has been posting patches for
that:
http://lwn.net/Articles/574950/
There's some active work in the trace and debug area too.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-05 20:35 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
2013-12-05 20:03 ` Rob Herring
2013-12-05 20:35 ` Mark Brown [this message]
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=20131205203519.GA29268@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=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