1 * Freescale QUICC Engine module (QE)
2 This represents qe module that is installed on PowerQUICC II Pro.
4 NOTE: This is an interim binding; it should be updated to fit
5 in with the CPM binding later in this document.
7 Basically, it is a bus of devices, that could act more or less
8 as a complete entity (UCC, USB etc ). All of them should be siblings on
9 the "root" qe node, using the common properties from there.
10 The description below applies to the qe of MPC8360 and
11 more nodes and properties would be extended in the future.
16 - compatible : should be "fsl,qe";
17 - model : precise model of the QE, Can be "QE", "CPM", or "CPM2"
18 - reg : offset and length of the device registers.
19 - bus-frequency : the clock frequency for QUICC Engine.
20 - fsl,qe-num-riscs: define how many RISC engines the QE has.
21 - fsl,qe-num-snums: define how many serial number(SNUM) the QE can use for the
25 - fsl,firmware-phandle:
26 Usage: required only if there is no fsl,qe-firmware child node
28 Definition: Points to a firmware node (see "QE Firmware Node" below)
29 that contains the firmware that should be uploaded for this QE.
30 The compatible property for the firmware node should say,
33 Recommended properties
34 - brg-frequency : the internal clock source frequency for baud-rate
41 #interrupt-cells = <2>;
42 compatible = "fsl,qe";
43 ranges = <0 e0100000 00100000>;
46 bus-frequency = <179A7B00>;
49 * Multi-User RAM (MURAM)
52 - compatible : should be "fsl,qe-muram", "fsl,cpm-muram".
53 - mode : the could be "host" or "slave".
54 - ranges : Should be defined as specified in 1) to describe the
55 translation of MURAM addresses.
56 - data-only : sub-node which defines the address area under MURAM
57 bus that can be allocated as data/parameter
62 compatible = "fsl,qe-muram", "fsl,cpm-muram";
63 ranges = <0 00010000 0000c000>;
66 compatible = "fsl,qe-muram-data",
74 This node defines a firmware binary that is embedded in the device tree, for
75 the purpose of passing the firmware from bootloader to the kernel, or from
76 the hypervisor to the guest.
78 The firmware node itself contains the firmware binary contents, a compatible
79 property, and any firmware-specific properties. The node should be placed
80 inside a QE node that needs it. Doing so eliminates the need for a
81 fsl,firmware-phandle property. Other QE nodes that need the same firmware
82 should define an fsl,firmware-phandle property that points to the firmware node
85 The fsl,firmware property can be specified in the DTS (possibly using incbin)
86 or can be inserted by the boot loader at boot time.
92 Definition: A standard property. Specify a string that indicates what
93 kind of firmware it is. For QE, this should be "fsl,qe-firmware".
97 Value type: <prop-encoded-array>, encoded as an array of bytes
98 Definition: A standard property. This property contains the firmware
103 compatible = "fsl,qe";
104 qe_firmware:qe-firmware {
105 compatible = "fsl,qe-firmware";
106 fsl,firmware = [0x70 0xcd 0x00 0x00 0x01 0x46 0x45 ...];
112 compatible = "fsl,qe";
113 fsl,firmware-phandle = <&qe_firmware>;