From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM64: juno: add SCPI mailbox protocol, clock and CPUFreq support
Date: Thu, 14 May 2015 16:42:30 +0100 [thread overview]
Message-ID: <1431618155-3132-1-git-send-email-sudeep.holla@arm.com> (raw)
Hi,
This patch series adds support for:
1. SCPI(System Control and Power Interface) mailbox protocol driver.
It uses ARM MHU mailbox controller driver on Juno but can work with
any mailbox controllers using standard mailbox APIs
2. Add support for clocks provided by SCP firmware through the SCPI
interface
3. Using the existing arm_big_little cpufreq driver and the newly
added SCPI clock driver, it also adds support for CPU DVFS on
ARM64 JUNO development platforms.
The SCPI protocol document is available @[1],[2]
Changes v1->v2:
- Updated the token handling in scpi driver as per Tixy's
suggestion along with other review comments
- Removed multiple drivers in scpi clock as Lorenzo suggested
- Added free_opp_table in scpi-cpufreq as Viresh suggested
- Separated the DT binding document
- Moved SCPI protocol driver to drivers/firmware
Regards,
Sudeep
[1] http://community.arm.com/servlet/JiveServlet/download/8401-45-18326/DUI0922B_scp_message_interface.pdf
[2] https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=DUI0922B_scp_message_interface.pdf
Sudeep Holla (5):
Documentation: add DT binding for ARM System Control and Power
Interface(SCPI) protocol
firmware: add support for ARM System Control and Power Interface(SCPI)
protocol
clk: add support for clocks provided by SCP(System Control Processor)
clk: scpi: add support for cpufreq virtual device
cpufreq: arm_big_little: add SCPI interface driver
Documentation/devicetree/bindings/arm/arm,scpi.txt | 121 ++++
drivers/clk/Kconfig | 10 +
drivers/clk/Makefile | 1 +
drivers/clk/clk-scpi.c | 305 +++++++++
drivers/cpufreq/Kconfig.arm | 9 +
drivers/cpufreq/Makefile | 1 +
drivers/cpufreq/scpi-cpufreq.c | 124 ++++
drivers/firmware/Kconfig | 19 +
drivers/firmware/Makefile | 1 +
drivers/firmware/arm_scpi.c | 713 +++++++++++++++++++++
include/linux/scpi_protocol.h | 57 ++
11 files changed, 1361 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/arm,scpi.txt
create mode 100644 drivers/clk/clk-scpi.c
create mode 100644 drivers/cpufreq/scpi-cpufreq.c
create mode 100644 drivers/firmware/arm_scpi.c
create mode 100644 include/linux/scpi_protocol.h
--
1.9.1
next reply other threads:[~2015-05-14 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 15:42 Sudeep Holla [this message]
2015-05-14 15:42 ` [PATCH v2 1/5] Documentation: add DT binding for ARM System Control and Power Interface(SCPI) protocol Sudeep Holla
2015-05-14 15:42 ` [PATCH v2 2/5] firmware: add support " Sudeep Holla
2015-05-20 11:17 ` Jon Medhurst (Tixy)
2015-05-26 11:18 ` Sudeep Holla
2015-05-14 15:42 ` [PATCH v2 3/5] clk: add support for clocks provided by SCP(System Control Processor) Sudeep Holla
2015-05-14 15:42 ` [PATCH v2 4/5] clk: scpi: add support for cpufreq virtual device Sudeep Holla
2015-05-14 15:42 ` [PATCH v2 5/5] cpufreq: arm_big_little: add SCPI interface driver Sudeep Holla
2015-05-14 22:03 ` Rafael J. Wysocki
2015-05-15 5:39 ` 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=1431618155-3132-1-git-send-email-sudeep.holla@arm.com \
--to=sudeep.holla@arm.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).