From: Rob Herring <robh@kernel.org>
To: Nava kishore Manne <nava.manne@xilinx.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
Nava kishore Manne <nava.manne@xilinx.com>,
linux-kernel@vger.kernel.org, Jolly Shah <jollys@xilinx.com>,
RAJANV@xilinx.com, robh+dt@kernel.org, michals@xilinx.com,
linux-arm-kernel@lists.infradead.org, chinnikishore369@gmail.com
Subject: Re: [PATCH v3 3/6] dt-bindings: reset: Add bindings for ZynqMP reset driver
Date: Mon, 21 Jan 2019 09:46:04 -0600 [thread overview]
Message-ID: <20190121154604.GA30149@bogus> (raw)
In-Reply-To: <20190121173835.21173-4-nava.manne@xilinx.com>
On Mon, 21 Jan 2019 23:08:32 +0530, Nava kishore Manne wrote:
> Add documentation to describe Xilinx ZynqMP reset driver
> bindings.
>
> Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com>
> Signed-off-by: Jolly Shah <jollys@xilinx.com>
> ---
> Changes for v3:
> -Moved reset outputs definitions info into
> a header file(xlnx-zynqmp-resets.h).
>
> .../bindings/reset/xlnx,zynqmp-reset.txt | 52 +++++++
> .../dt-bindings/reset/xlnx-zynqmp-resets.h | 130 ++++++++++++++++++
> 2 files changed, 182 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reset/xlnx,zynqmp-reset.txt
> create mode 100644 include/dt-bindings/reset/xlnx-zynqmp-resets.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-21 15:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 17:38 [PATCH v3 0/6] dt-bindings: Firmware node binding for ZynqMP core Nava kishore Manne
2019-01-21 17:38 ` [PATCH v3 1/6] dt-bindings: power: Add ZynqMP power domain bindings Nava kishore Manne
2019-01-21 17:38 ` [PATCH v3 2/6] dt-bindings: soc: Add ZynqMP PM bindings Nava kishore Manne
2019-01-21 17:38 ` [PATCH v3 3/6] dt-bindings: reset: Add bindings for ZynqMP reset driver Nava kishore Manne
2019-01-21 15:46 ` Rob Herring [this message]
2019-01-21 17:38 ` [PATCH v3 4/6] dt-bindings: pinctrl: Add ZynqMP pin controller bindings Nava kishore Manne
2019-01-21 17:38 ` [PATCH v3 5/6] dt-bindings: nvmem: Add bindings for ZynqMP nvmem driver Nava kishore Manne
2019-01-21 15:47 ` Rob Herring
2019-01-21 17:38 ` [PATCH v3 6/6] dt-bindings: fpga: Add bindings for ZynqMP fpga driver Nava kishore Manne
2019-01-21 15:49 ` Rob Herring
[not found] ` <BYAPR02MB4710D1404CF2816599623363C2980@BYAPR02MB4710.namprd02.prod.outlook.com>
2019-02-22 20:30 ` Rob Herring
2019-03-04 11:35 ` Nava kishore Manne
2019-03-04 17:27 ` Rob Herring
2019-03-05 9:42 ` Nava kishore Manne
2019-03-13 20:07 ` Rob Herring
2019-03-13 5:28 ` Nava kishore Manne
-- strict thread matches above, loose matches on Subject: below --
2019-01-21 17:24 [PATCH v3 0/6] dt-bindings: Firmware node binding for ZynqMP core Nava kishore Manne
2019-01-21 17:24 ` [PATCH v3 3/6] dt-bindings: reset: Add bindings for ZynqMP reset driver Nava kishore Manne
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=20190121154604.GA30149@bogus \
--to=robh@kernel.org \
--cc=RAJANV@xilinx.com \
--cc=chinnikishore369@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jollys@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michals@xilinx.com \
--cc=nava.manne@xilinx.com \
--cc=robh+dt@kernel.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).