[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1437649828-14540-1-git-send-email-sudeep.holla@arm.com>
Date: Thu, 23 Jul 2015 12:10:20 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: linux-kernel@...r.kernel.org
Cc: Sudeep Holla <sudeep.holla@....com>,
Liviu Dudau <liviu.dudau@....com>,
Punit Agrawal <punit.agrawal@....com>,
"Jon Medhurst (Tixy)" <tixy@...aro.org>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
Kevin Hilman <khilman@...nel.org>
Subject: [PATCH v5 0/8] ARM64: juno: add SCPI mailbox protocol, clock and CPUFreq support
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 v4->v5:
- Updated the SCPI clock bindings to correct the clock specifier
usage and other minor updates as per review feedback
- Updated clock driver to use SCPI specifier clock specifier
decode function
- Minor reshuffling in Juno DTS files, no functionality change
- Added ACKs recieved so far
Changes v3->v4:
- Updated the SCPI binding based on MarkR's feedback
- Updated SCPI clock driver to incorporate Stephen Boyd's review
comments + used clk_set_rate_range to limit the clock range
- Since no major changes are expected in SCPI DT, updated the
Juno DTS to support SCPI and dependent device nodes.
Changes v2->v3:
- Minor fix in SCPI driver and added Tixy's reviewed-by tag
- Updated scpi clock driver to incorporate all the comments from
Stephen
- Added Viresh's ack
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
v1: https://lkml.org/lkml/2015/4/27/232
v2: https://lkml.org/lkml/2015/5/14/470
v3: https://lkml.org/lkml/2015/5/27/220
v4: https://lkml.org/lkml/2015/6/8/178
*** BLURB HERE ***
Sudeep Holla (8):
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
arm64: dts: add SRAM, MHU mailbox and SCPI support on Juno
arm64: dts: add CPU topology on Juno
arm64: dts: add clock support for all the cpus
Documentation/devicetree/bindings/arm/arm,scpi.txt | 151 +++++
MAINTAINERS | 10 +
arch/arm64/boot/dts/arm/juno-base.dtsi | 54 ++
arch/arm64/boot/dts/arm/juno-r1.dts | 32 +
arch/arm64/boot/dts/arm/juno.dts | 32 +
drivers/clk/Kconfig | 10 +
drivers/clk/Makefile | 1 +
drivers/clk/clk-scpi.c | 324 ++++++++++
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 | 711 +++++++++++++++++++++
include/linux/scpi_protocol.h | 61 ++
15 files changed, 1540 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists