On 16/08/17 13:24, Michal Simek wrote: > From: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx> > > Document the DT bindings for the Zynq UltraScale+ PM Firmware. > > Signed-off-by: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx> > Signed-off-by: Michal Simek <michal.simek@xxxxxxxxxx> > --- > > Changes in v2: > - Move to bindings/firmware and also add it to firmware node > Reported-by Rob > > .../bindings/firmware/xlnx,zynqmp-pm.txt | 22 ++++++++++++++++++++++ > 1 file changed, 22 insertions(+) > create mode 100644 Documentation/devicetree/bindings/firmware/xlnx,zynqmp-pm.txt > > diff --git a/Documentation/devicetree/bindings/firmware/xlnx,zynqmp-pm.txt b/Documentation/devicetree/bindings/firmware/xlnx,zynqmp-pm.txt > new file mode 100644 > index 000000000000..7de0c82758b3 > --- /dev/null > +++ b/Documentation/devicetree/bindings/firmware/xlnx,zynqmp-pm.txt > @@ -0,0 +1,22 @@ > +Xilinx Zynq MPSoC Firmware Device Tree Bindings > + > +The zynqmp-pm node describes the interface to platform firmware. > + > +Required properties: > + - compatible: Must contain: "xlnx,zynqmp-pm" > + - method: The method of calling the PM-API firmware layer. > + Permitted values are: > + - "smc" : To be used in configurations without a hypervisor > + - "hvc" : To be used when hypervisor is present > + - interrupts: Interrupt specifier What exactly is this interrupt ? I see it's not SGI, so if it's SPI, where does this originate from ? How is that dealt ? -- Regards, Sudeep -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
