From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC V1 0/8] CPUFreq: create platform-dev for DT based cpufreq drivers
Date: Tue, 2 Dec 2014 09:20:13 +0100 [thread overview]
Message-ID: <20141202092013.6017a9b0@free-electrons.com> (raw)
In-Reply-To: <3594266.ci9lGXQ9iA@wuerfel>
Dear Arnd Bergmann,
On Mon, 01 Dec 2014 15:59:14 +0100, Arnd Bergmann wrote:
> I still don't see where it does that. All I see for mvebu is
>
> platform_device_register_simple("cpufreq-dt", -1, NULL, 0);
>
> without any platform data. I see this patch
> http://lists.linaro.org/pipermail/linaro-kernel/2014-September/017693.html
> on the mailing list, but it's not in linux-next, and it obviously
> would not work any more with the patch I proposed. Instead I suppose
> you would use a different string to match against for the case of
> separate clocks.
Hum, right. Actually, only the cpufreq driver part has been taken, and
I forgot to resubmit the mach-mvebu part of the solution. I'll do so
today.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-02 8:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 11:41 [RFC V1 0/8] CPUFreq: create platform-dev for DT based cpufreq drivers Viresh Kumar
2014-12-01 11:41 ` [RFC V1 1/8] cpufreq: Reuse "compatible" binding to probe " Viresh Kumar
2014-12-01 11:41 ` [RFC V1 2/8] cpufreq: Create cpufreq platform-device based on "compatible" from DT Viresh Kumar
2014-12-01 11:41 ` [RFC V1 3/8] cpufreq: imx: reuse dt_device.c to create cpufreq platform device Viresh Kumar
2014-12-01 11:41 ` [RFC V1 4/8] cpufreq: mvebu: " Viresh Kumar
2014-12-01 11:41 ` [RFC V1 5/8] cpufreq: shmobile: " Viresh Kumar
2014-12-01 11:41 ` [RFC V1 6/8] cpufreq: zynq: " Viresh Kumar
2014-12-01 11:41 ` [RFC V1 7/8] cpufreq: calxeda: " Viresh Kumar
2014-12-01 11:41 ` [RFC V1 8/8] cpufreq: exynos: " Viresh Kumar
2014-12-01 12:54 ` [RFC V1 0/8] CPUFreq: create platform-dev for DT based cpufreq drivers Arnd Bergmann
2014-12-01 13:29 ` Viresh Kumar
2014-12-01 13:35 ` Sudeep Holla
2014-12-01 14:11 ` Arnd Bergmann
2014-12-01 14:48 ` Viresh Kumar
2014-12-01 15:07 ` Sudeep Holla
2014-12-01 16:03 ` Arnd Bergmann
2014-12-01 16:56 ` Sudeep Holla
2014-12-01 14:05 ` Arnd Bergmann
2014-12-01 14:48 ` Viresh Kumar
2014-12-01 14:59 ` Arnd Bergmann
2014-12-02 8:20 ` Thomas Petazzoni [this message]
2014-12-01 18:14 ` Rob Herring
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=20141202092013.6017a9b0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).