From: Mark Rutland <mark.rutland@arm.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
edgar.iglesias@xilinx.com, Rob Herring <robh@kernel.org>,
Soren Brinkmann <soren.brinkmann@xilinx.com>,
devicetree@vger.kernel.org, monstr@monstr.eu,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCHv2 1/3] dt: xilinx: zynqmp: Add bindings for PM firmware
Date: Wed, 16 Aug 2017 17:00:46 +0100 [thread overview]
Message-ID: <20170816160046.GB12389@leverpostej> (raw)
In-Reply-To: <2935be9896d54020720919e7dab7c2f86bdc83a3.1502886277.git.michal.simek@xilinx.com>
On Wed, Aug 16, 2017 at 02:24:56PM +0200, Michal Simek wrote:
> From: Soren Brinkmann <soren.brinkmann@xilinx.com>
>
> Document the DT bindings for the Zynq UltraScale+ PM Firmware.
>
> Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
>
> 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.
Is there any documentation for this? I appreciate that the answer
might be "no".
> +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
For what, exactly?
Is this an interrupt for FW to signal the OS somehow?
If so, is it an SGI?
Thanks,
Mark.
next prev parent reply other threads:[~2017-08-16 16:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 12:24 [PATCHv2 0/3] arm64 xilinx zynqmp firmware interface Michal Simek
2017-08-16 12:24 ` [PATCHv2 1/3] dt: xilinx: zynqmp: Add bindings for PM firmware Michal Simek
2017-08-16 15:45 ` Sudeep Holla
2017-08-17 6:27 ` Michal Simek
2017-08-16 16:00 ` Mark Rutland [this message]
2017-08-17 6:26 ` Michal Simek
2017-08-16 12:24 ` [PATCHv2 2/3] arm64: zynqmp: dt: Add PM firmware node Michal Simek
2017-08-16 12:24 ` [PATCHv2 3/3] soc: xilinx: zynqmp: Add firmware interface Michal Simek
2017-08-16 15:58 ` Mark Rutland
2017-08-17 6:57 ` Michal Simek
2017-08-16 15:39 ` [PATCHv2 0/3] arm64 xilinx zynqmp " Marc Zyngier
2017-08-17 6:10 ` Michal Simek
2017-08-17 7:52 ` Marc Zyngier
2017-08-17 8:42 ` Michal Simek
2017-08-17 9:12 ` Sudeep Holla
2017-08-17 10:32 ` Michal Simek
2017-08-17 11:18 ` Sudeep Holla
2017-08-17 11:24 ` Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170816160046.GB12389@leverpostej \
--to=mark.rutland@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=edgar.iglesias@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=soren.brinkmann@xilinx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox