blob: 0a1e858225feedb03a30824e487fad17375f0b6a [file] [log] [blame]
Lokesh Vutlafdae32e2018-08-27 15:57:52 +05301Texas Instruments' K3 Remote processor driver
2=============================================
3
4In K3 generation Socs, loading an image on any processing entity
5cannot be done directly from U-Boot. In order to load an image,
6remoteproc driver should communicate to SYSFW with a specific sequence.
7Also enable the timer required for this remotecore.
8
9Required properties:
10--------------------
11- compatible: Shall be: "ti,am654-rproc"
12- reg: base address of the remoteproc timer.
13- power-domains: Should contain two sets of entries:
14 First set corresponds to pm domain of the
15 remotecore timer. Seconf entry corresponds to the
16 remoteproc to start.
17 This property is as per the binding,
18 doc/device-tree-bindings/power/ti,sci-pm-domain.txt
19- resets: Should contain a phandle to a reset controller node
20 and an args specifier containing the remote code
21 device id and reset mask value. This is as per the
22 doc/device-tree-bindings/reset/ti,sci-reset.txt
23- ti,sci: Phandle to TI-SCI compatible System controller node.
24- ti,sci-proc-id: Processor id as identified by TISCI
25
26Optional properties:
27--------------------
28- assigned-clocks: Should contain a phandle to clock node and an args
29 specifier containing the remote core device id and
30 the clock id within the remote core. This is as per
31 doc/device-tree-bindings/clock/ti,sci-clk.txt
32- assigned-clock-rates: One entry for each entry of assigned-clocks. This is
33 the frequency at which the corresponding clock needs
34 to be assigned.
35- ti,sci-host-id: Host ID to which the processor control is transferred to
36
37Example:
38---------
39
40a53_0: a53@0 {
41 compatible = "ti,am654-rproc";
42 power-domains = <&k3_pds 61>,
43 <&k3_pds 202>;
44 resets = <&k3_reset 202 0>;
45 assigned-clocks = <&k3_clks 202 0>;
46 assigned-clock-rates = <800000000>;
47 ti,sci = <&dmsc>;
48 ti,sci-proc-id = <32>;
49 ti,sci-host-id = <10>;
50};