devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
To: Michal Simek
	<michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>,
	edgar.iglesias-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org,
	Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Soren Brinkmann
	<soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Subject: Re: [PATCHv2 1/3] dt: xilinx: zynqmp: Add bindings for PM firmware
Date: Wed, 16 Aug 2017 16:45:28 +0100	[thread overview]
Message-ID: <2c2ffced-bc32-1eb4-aabe-ad6386076267@arm.com> (raw)
In-Reply-To: <2935be9896d54020720919e7dab7c2f86bdc83a3.1502886277.git.michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>



On 16/08/17 13:24, Michal Simek wrote:
> From: Soren Brinkmann <soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
> 
> Document the DT bindings for the Zynq UltraScale+ PM Firmware.
> 
> Signed-off-by: Soren Brinkmann <soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
> Signed-off-by: Michal Simek <michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
> ---
> 
> 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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-08-16 15:45 UTC|newest]

Thread overview: 15+ 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
     [not found]   ` <2935be9896d54020720919e7dab7c2f86bdc83a3.1502886277.git.michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2017-08-16 15:45     ` Sudeep Holla [this message]
     [not found]       ` <2c2ffced-bc32-1eb4-aabe-ad6386076267-5wv7dgnIgG8@public.gmane.org>
2017-08-17  6:27         ` Michal Simek
2017-08-16 16:00     ` Mark Rutland
2017-08-17  6:26       ` Michal Simek
2017-08-16 12:24 ` [PATCHv2 2/3] arm64: zynqmp: dt: Add PM firmware node Michal Simek
     [not found] ` <cover.1502886277.git.michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2017-08-16 15:39   ` [PATCHv2 0/3] arm64 xilinx zynqmp firmware interface Marc Zyngier
     [not found]     ` <43deeed7-32c8-7914-5f44-862ebbe14a3b-5wv7dgnIgG8@public.gmane.org>
2017-08-17  6:10       ` Michal Simek
2017-08-17  7:52         ` Marc Zyngier
     [not found]           ` <a1970cb5-1cf1-d38a-3de3-c782c23fc8ac-5wv7dgnIgG8@public.gmane.org>
2017-08-17  8:42             ` Michal Simek
     [not found]               ` <0560c79f-e461-6010-0628-e99ce0a1f8c6-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2017-08-17  9:12                 ` Sudeep Holla
2017-08-17 10:32                   ` Michal Simek
     [not found]                     ` <07473fe2-d159-a016-2f65-735b1231beb8-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
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=2c2ffced-bc32-1eb4-aabe-ad6386076267@arm.com \
    --to=sudeep.holla-5wv7dgnigg8@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=edgar.iglesias-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).