Merge branch 'for-4.10-ti-sci-base' of https://github.com/t-kristo/linux-pm into next/drivers

Texas Instruments System Control Interface (TI-SCI) Message Protocol

--------------------------------------------------------------------

Texas Instrument's processors including those belonging to Keystone generation

of processors have separate hardware entity which is now responsible for the

management of the System on Chip (SoC) system. These include various system

level functions as well.

An example of such an SoC is K2G, which contains the system control hardware

block called Power Management Micro Controller (PMMC). This hardware block is

initialized early into boot process and provides services to Operating Systems

on multiple processors including ones running Linux.

See http://processors.wiki.ti.com/index.php/TISCI for protocol definition.

TI-SCI controller Device Node:

=============================

The TI-SCI node describes the Texas Instrument's System Controller entity node.

This parent node may optionally have additional children nodes which describe

specific functionality such as clocks, power domain, reset or additional

functionality as may be required for the SoC. This hierarchy also describes the

relationship between the TI-SCI parent node to the child node.

Required properties:

-------------------

- compatible: should be "ti,k2g-sci"

- mbox-names:

	"rx" - Mailbox corresponding to receive path

	"tx" - Mailbox corresponding to transmit path

- mboxes: Mailboxes corresponding to the mbox-names. Each value of the mboxes

	  property should contain a phandle to the mailbox controller device

	  node and an args specifier that will be the phandle to the intended

	  sub-mailbox child node to be used for communication.

See Documentation/devicetree/bindings/mailbox/mailbox.txt for more details

about the generic mailbox controller and client driver bindings. Also see

Documentation/devicetree/bindings/mailbox/ti,message-manager.txt for typical

controller that is used to communicate with this System controllers.

Optional Properties:

-------------------

- reg-names:

	debug_messages - Map the Debug message region

- reg:  register space corresponding to the debug_messages

- ti,system-reboot-controller: If system reboot can be triggered by SoC reboot

Example (K2G):

-------------

	pmmc: pmmc {

		compatible = "ti,k2g-sci";

		mbox-names = "rx", "tx";

		mboxes= <&msgmgr &msgmgr_proxy_pmmc_rx>,

			<&msgmgr &msgmgr_proxy_pmmc_tx>;

		reg-names = "debug_messages";

		reg = <0x02921800 0x800>;

	};

TI-SCI Client Device Node:

=========================

Client nodes are maintained as children of the relevant TI-SCI device node.

Example (K2G):

-------------

	pmmc: pmmc {

		compatible = "ti,k2g-sci";

		...

		my_clk_node: clk_node {

			...

			...

		};

		my_pd_node: pd_node {

			...

			...

		};

	};

F:	arch/xtensa/

F:	drivers/irqchip/irq-xtensa-*

Texas Instruments' System Control Interface (TISCI) Protocol Driver

M:	Nishanth Menon <nm@ti.com>

M:	Tero Kristo <t-kristo@ti.com>

M:	Santosh Shilimkar <ssantosh@kernel.org>

L:	linux-arm-kernel@lists.infradead.org

S:	Maintained

F:	Documentation/devicetree/bindings/arm/keystone/ti,sci.txt

F:	drivers/firmware/ti_sci*

F:	include/linux/soc/ti/ti_sci_protocol.h

THANKO'S RAREMONO AM/FM/SW RADIO RECEIVER USB DRIVER

M:	Hans Verkuil <hverkuil@xs4all.nl>

L:	linux-media@vger.kernel.org

	def_bool y

	depends on QCOM_SCM && ARM64

config TI_SCI_PROTOCOL

	tristate "TI System Control Interface (TISCI) Message Protocol"

	depends on TI_MESSAGE_MANAGER

	help

	  TI System Control Interface (TISCI) Message Protocol is used to manage

	  compute systems such as ARM, DSP etc with the system controller in

	  complex System on Chip(SoC) such as those found on certain keystone

	  generation SoC from TI.

	  System controller provides various facilities including power

	  management function support.

	  This protocol library is used by client drivers to use the features

	  provided by the system controller.

config HAVE_ARM_SMCCC

	bool

obj-$(CONFIG_QCOM_SCM_64)	+= qcom_scm-64.o

obj-$(CONFIG_QCOM_SCM_32)	+= qcom_scm-32.o

CFLAGS_qcom_scm-32.o :=$(call as-instr,.arch armv7-a\n.arch_extension sec,-DREQUIRES_SEC=1) -march=armv7-a

obj-$(CONFIG_TI_SCI_PROTOCOL)	+= ti_sci.o

obj-y				+= broadcom/

obj-y				+= meson/