Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit a90b15e0 authored by Sudeep Holla's avatar Sudeep Holla
Browse files

Documentation: bindings: decouple juno specific details from generic binding 



Since SCPI is a generic protocol and the bindings are intended to be
generic, we need to decouple all the platform specific binding details
out of the generic bindings.

This patch moves are the Juno platform specific details into a separate
binding document.

Acked-by: default avatarRob Herring <robh@kernel.org>
Signed-off-by: default avatarSudeep Holla <sudeep.holla@arm.com>
parent abd3e805

Documentation/devicetree/bindings/arm/arm,scpi.txt

+7 −13
Original line number Diff line number Diff line
@@ -59,18 +59,14 @@ SRAM and Shared Memory for SCPI 
A small area of SRAM is reserved for SCPI communication between application

processors and SCP.



Required properties:

- compatible : should be "arm,juno-sram-ns" for Non-secure SRAM on Juno



The rest of the properties should follow the generic mmio-sram description

found in ../../sram/sram.txt

The properties should follow the generic mmio-sram description found in [3]



Each sub-node represents the reserved area for SCPI.



Required sub-node properties:

- reg : The base offset and size of the reserved area with the SRAM

- compatible : should be "arm,juno-scp-shmem" for Non-secure SRAM based

	       shared memory on Juno platforms

- compatible : should be "arm,scp-shmem" for Non-secure SRAM based

	       shared memory



Sensor bindings for the sensors based on SCPI Message Protocol

--------------------------------------------------------------
@@ -81,11 +77,9 @@ Required properties: 
- #thermal-sensor-cells: should be set to 1. This property follows the

			 thermal device tree bindings[2].



			 Valid cell values are raw identifiers (Sensor

			 ID) as used by the firmware. Refer to

			 platform documentation for your

			 implementation for the IDs to use. For Juno

			 R0 and Juno R1 refer to [3].

			 Valid cell values are raw identifiers (Sensor ID)

			 as used by the firmware. Refer to  platform details

			 for your implementation for the IDs to use.



Power domain bindings for the power domains based on SCPI Message Protocol

------------------------------------------------------------
@@ -112,7 +106,7 @@ Required properties: 
[0] http://infocenter.arm.com/help/topic/com.arm.doc.dui0922b/index.html

[1] Documentation/devicetree/bindings/clock/clock-bindings.txt

[2] Documentation/devicetree/bindings/thermal/thermal.txt

[3] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/apas03s22.html

[3] Documentation/devicetree/bindings/sram/sram.txt

[4] Documentation/devicetree/bindings/power/power_domain.txt



Example:

Documentation/devicetree/bindings/arm/juno,scpi.txt

0 → 100644
+26 −0
Original line number Diff line number Diff line 
System Control and Power Interface (SCPI) Message Protocol

(in addition to the standard binding in [0])



Juno SRAM and Shared Memory for SCPI

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



Required properties:

- compatible : should be "arm,juno-sram-ns" for Non-secure SRAM



Each sub-node represents the reserved area for SCPI.



Required sub-node properties:

- reg : The base offset and size of the reserved area with the SRAM

- compatible : should be "arm,juno-scp-shmem" for Non-secure SRAM based

	       shared memory on Juno platforms



Sensor bindings for the sensors based on SCPI Message Protocol

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

Required properties:

- compatible : should be "arm,scpi-sensors".

- #thermal-sensor-cells: should be set to 1.

			 For Juno R0 and Juno R1 refer to [1] for the

			 sensor identifiers



[0] Documentation/devicetree/bindings/arm/arm,scpi.txt

[1] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/apas03s22.html