From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver
Date: Fri, 19 Aug 2016 17:51:54 -0500 [thread overview]
Message-ID: <20160819225159.10758-1-nm@ti.com> (raw)
Hi,
Texas Instruments' Keystone generation System on Chips (SoC)
starting with 66AK2G02[1], now include a dedicated SoC System Control
entity called PMMC(Power Management Micro Controller) in line with
ARM architecture recommendations. The function of this module is
to integrate all system operations in a centralized location.
Communication with the SoC System Control entity from various
processing units like ARM/DSP occurs over Message Manager hardware
block.
This series adds the base support for TI System Control Interface
(TI-SCI) protocol[2]. The protocol is built on top of Texas
Instrument's Message Manager communication mechanism[3].
Overall architecture is very similar to SCPI[4] as follows:
+-------------+ +---------+ +------^-----+
| TI SCI GENPD| |TISCI Clk| |TISCI reset |
+------+------+ +----+----+ +------+-----+
| | |
| +----v--------------+ |
+----------> TISCI Protocol(*) <--+
+----+--------------+
|
+---v-----------+
| MAILBOX FWK |
+---+-----------+
|
+---v-----------+
| TI MSGMGR |-> TISCI hardware block
+---------------+
(*) This series.
NOTE: Given that this is fundamental to the Keystone generation of SoC
starting with K2G, I have taken the liberty of adding Santosh, Tero
and myself as maintainers to these driver. Do let me know if that is
not appropriate.
[1] http://www.ti.com/product/66ak2g02
[2] http://processors.wiki.ti.com/index.php/TISCI
[3] Documentation/devicetree/bindings/mailbox/ti,message-manager.txt
[4] Documentation/devicetree/bindings/arm/arm,scpi.txt
Baseline: v4.8-rc1
boot log: http://pastebin.ubuntu.com/23071570/ (with additional SoC specific dts patches)
Patches can also be found: https://github.com/nmenon/linux-2.6-playground/commits/upstream/v4.9/tisci-base-v1
PS: We believe the churn is done in the protocol over the last 2 TI
vendor kernel versions and minimal changes may be involved in the
future. Obviously, a lot of folks (especially Russ Dill) have been
involved in making this happen.. unfortunately, the list is a bit too
long to elaborate here :(
Nishanth Menon (5):
Documentation: Add support for TI System Control Interface (TI-SCI)
protocol
firmware: Add basic support for TI System Control Interface (TI-SCI)
protocol
firmware: ti_sci: Add support for Device control
firmware: ti_sci: Add support for Clock control
firmware: ti_sci: Add support for reboot core service
.../devicetree/bindings/arm/keystone/ti,sci.txt | 66 +
MAINTAINERS | 10 +
drivers/firmware/Kconfig | 15 +
drivers/firmware/Makefile | 1 +
drivers/firmware/ti_sci.c | 1993 ++++++++++++++++++++
drivers/firmware/ti_sci.h | 492 +++++
include/linux/soc/ti/ti_sci_protocol.h | 249 +++
7 files changed, 2826 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/keystone/ti,sci.txt
create mode 100644 drivers/firmware/ti_sci.c
create mode 100644 drivers/firmware/ti_sci.h
create mode 100644 include/linux/soc/ti/ti_sci_protocol.h
--
2.9.1.200.gb1ec08f
next reply other threads:[~2016-08-19 22:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 22:51 Nishanth Menon [this message]
2016-08-19 22:51 ` [PATCH 1/5] Documentation: Add support for TI System Control Interface (TI-SCI) protocol Nishanth Menon
2016-08-19 22:51 ` [PATCH 2/5] firmware: Add basic " Nishanth Menon
2016-08-21 16:20 ` Lokesh Vutla
2016-08-23 18:38 ` Nishanth Menon
2016-08-19 22:51 ` [PATCH 3/5] firmware: ti_sci: Add support for Device control Nishanth Menon
2016-08-22 3:56 ` Lokesh Vutla
2016-08-23 18:45 ` Nishanth Menon
2016-08-29 22:30 ` Santosh Shilimkar
2016-08-19 22:51 ` [PATCH 4/5] firmware: ti_sci: Add support for Clock control Nishanth Menon
2016-08-19 22:51 ` [PATCH 5/5] firmware: ti_sci: Add support for reboot core service Nishanth Menon
2016-08-23 17:48 ` Rob Herring
2016-08-23 18:46 ` Nishanth Menon
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=20160819225159.10758-1-nm@ti.com \
--to=nm@ti.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