From: Andrew Lunn <andrew@lunn.ch>
To: mark.rutland@arm.com
Cc: rjw@rjwysocki.net, Jason Cooper <jason@lakedaemon.net>,
linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-pm@vger.kernel.org,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
Andrew Lunn <andrew@lunn.ch>
Subject: [RFC PATCH v5 0/4] Dove Cpufreq driver
Date: Tue, 17 Dec 2013 22:41:09 +0100 [thread overview]
Message-ID: <1387316473-3250-1-git-send-email-andrew@lunn.ch> (raw)
In-Reply-To: <20131204145413.GD29200@e106331-lin.cambridge.arm.com>
This is an RFC where i attempt to address Mark Rutland's request for a
PMU node in DT, and all clocks and interrupts required by the cpufreq
driver are within this node. I would like to receive comments about
this binding.
This version does not address any other comments made to the code. I
will fix those issues once the binding is mostly decided.
Thanks
Andrew
Andrew Lunn (4):
cpufreq: Add a cpufreq driver for Marvell Dove
mvebu: Dove: Indicate the architecture supports cpufreq.
mvebu: Dove: Enable cpufreq driver in defconfig
mvebu: Dove: Add PMU node for cpufreq driver
.../devicetree/bindings/cpufreq/cpufreq-dove.txt | 23 ++
arch/arm/Kconfig | 1 +
arch/arm/boot/dts/dove.dtsi | 10 +
arch/arm/configs/dove_defconfig | 2 +
drivers/cpufreq/Kconfig.arm | 5 +
drivers/cpufreq/Makefile | 1 +
drivers/cpufreq/dove-cpufreq.c | 265 +++++++++++++++++++++
7 files changed, 307 insertions(+)
create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-dove.txt
create mode 100644 drivers/cpufreq/dove-cpufreq.c
--
1.8.5.1
next prev parent reply other threads:[~2013-12-17 21:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 14:17 [PATCH v4 0/4] Dove cpufreq driver Andrew Lunn
2013-12-04 14:17 ` [PATCH v4 1/4] cpufreq: Add a cpufreq driver for Marvell Dove Andrew Lunn
2013-12-04 14:33 ` Jason Cooper
2013-12-04 14:56 ` Andrew Lunn
2013-12-04 15:01 ` Jason Cooper
2013-12-04 14:54 ` Mark Rutland
2013-12-04 15:27 ` Andrew Lunn
2013-12-05 18:23 ` Mark Rutland
2013-12-17 21:41 ` Andrew Lunn [this message]
2013-12-17 21:41 ` [RFC PATCH v5 " Andrew Lunn
2013-12-20 3:32 ` Jason Cooper
2013-12-21 16:26 ` Andrew Lunn
2013-12-21 19:25 ` Jason Cooper
2013-12-21 21:54 ` Andrew Lunn
2013-12-22 4:00 ` Jason Cooper
2013-12-17 21:41 ` [RFC PATCH v5 2/4] mvebu: Dove: Indicate the architecture supports cpufreq Andrew Lunn
2013-12-17 21:41 ` [RFC PATCH v5 3/4] mvebu: Dove: Enable cpufreq driver in defconfig Andrew Lunn
2013-12-17 21:41 ` [RFC PATCH v5 4/4] mvebu: Dove: Add PMU node for cpufreq driver Andrew Lunn
2013-12-16 8:40 ` [PATCH v4 1/4] cpufreq: Add a cpufreq driver for Marvell Dove Viresh Kumar
2013-12-17 22:06 ` Andrew Lunn
2013-12-04 14:17 ` [PATCH v4 2/4] mvebu: Dove: Instantiate cpufreq driver Andrew Lunn
2013-12-04 14:36 ` Mark Rutland
2013-12-04 15:02 ` Andrew Lunn
2013-12-05 17:54 ` Mark Rutland
2013-12-05 18:29 ` Andrew Lunn
2013-12-08 0:50 ` Jason Cooper
2013-12-04 14:17 ` [PATCH v4 3/4] mvebu: Dove: Enable cpufreq driver in defconfig Andrew Lunn
2013-12-04 14:17 ` [PATCH v4 4/4] mvebu: Dove: Add clocks and DFS interrupt to cpu node in DT Andrew Lunn
2013-12-04 14:39 ` Mark Rutland
2013-12-04 14:55 ` Mark Rutland
2013-12-04 14:43 ` Jason Cooper
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=1387316473-3250-1-git-send-email-andrew@lunn.ch \
--to=andrew@lunn.ch \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=sebastian.hesselbarth@googlemail.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;
as well as URLs for NNTP newsgroup(s).