~hc/RK356X_SDK_RELEASE.git

..	..	@@ -78,8 +78,8 @@
78	78
79	79	Required properties:
80	80
81		-- compatible: "marvell,armada-7k-pinctrl",
82		- "marvell,armada-8k-cpm-pinctrl" or "marvell,armada-8k-cps-pinctrl"
	81	+- compatible: "marvell,armada-7k-pinctrl", "marvell,armada-8k-cpm-pinctrl",
	82	+ "marvell,armada-8k-cps-pinctrl" or "marvell,cp115-standalone-pinctrl"
83	83	depending on the specific variant of the SoC being used.
84	84
85	85	Available mpp pins/groups and functions:
..	..	@@ -199,8 +199,11 @@
199	199	The thermal IP can probe the temperature all around the processor. It
200	200	may feature several channels, each of them wired to one sensor.
201	201
	202	+It is possible to setup an overheat interrupt by giving at least one
	203	+critical point to any subnode of the thermal-zone node.
	204	+
202	205	For common binding part and usage, refer to
203		-Documentation/devicetree/bindings/thermal/thermal.txt
	206	+Documentation/devicetree/bindings/thermal/thermal*.yaml
204	207
205	208	Required properties:
206	209	- compatible: must be one of:
..	..	@@ -208,6 +211,11 @@
208	211	- reg: register range associated with the thermal functions.
209	212
210	213	Optional properties:
	214	+- interrupts-extended: overheat interrupt handle. Should point to
	215	+ a line of the ICU-SEI irqchip (116 is what is usually used by the
	216	+ firmware). The ICU-SEI will redirect towards interrupt line #37 of the
	217	+ AP SEI which is shared across all CPs.
	218	+ See interrupt-controller/interrupts.txt
211	219	- #thermal-sensor-cells: shall be <1> when thermal-zones subnodes refer
212	220	to this IP and represents the channel ID. There is one sensor per
213	221	channel. O refers to the thermal IP internal channel.
..	..	@@ -220,6 +228,7 @@
220	228	CP110_LABEL(thermal): thermal-sensor@70 {
221	229	compatible = "marvell,armada-cp110-thermal";
222	230	reg = <0x70 0x10>;
	231	+ interrupts-extended = <&CP110_LABEL(icu_sei) 116 IRQ_TYPE_LEVEL_HIGH>;
223	232	#thermal-sensor-cells = <1>;
224	233	};
225	234	};