From: Michal Simek <michal.simek@xilinx.com>
To: Nava kishore Manne <nava.manne@xilinx.com>,
<srinivas.kandagatla@linaro.org>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <michal.simek@xilinx.com>,
<jollys@xilinx.com>, <rajanv@xilinx.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <chinnikishore369@gmail.com>
Subject: Re: [PATCH v3 0/3] Add nvmem driver support for ZynqMP
Date: Tue, 5 Feb 2019 13:27:07 +0100 [thread overview]
Message-ID: <a6c443e3-a9ba-ffa3-5f0f-69db6884646d@xilinx.com> (raw)
In-Reply-To: <20190206110721.27765-1-nava.manne@xilinx.com>
On 06. 02. 19 12:07, Nava kishore Manne wrote:
> Nava kishore Manne (3):
> firmware: xilinx: Add zynqmp_pm_get_chipid() API
> dt-bindings: nvmem: Add bindings for ZynqMP nvmem driver
> nvmem: zynqmp: Added zynqmp nvmem firmware driver
>
> .../bindings/nvmem/xlnx,zynqmp-nvmem.txt | 47 ++++++++++
> drivers/firmware/xilinx/zynqmp.c | 24 ++++++
> drivers/nvmem/Kconfig | 10 +++
> drivers/nvmem/Makefile | 2 +
> drivers/nvmem/zynqmp_nvmem.c | 86 +++++++++++++++++++
> include/linux/firmware/xlnx-zynqmp.h | 2 +
> 6 files changed, 171 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/xlnx,zynqmp-nvmem.txt
> create mode 100644 drivers/nvmem/zynqmp_nvmem.c
>
Applied all with one small change in 1/3 by using number 24 instead of
22 to be aligned with firmware.
Patches are available here.
https://github.com/Xilinx/linux-xlnx/tree/zynqmp/soc
Thanks,
Michal
next prev parent reply other threads:[~2019-02-05 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 11:07 Nava kishore Manne
2019-02-05 12:27 ` Michal Simek [this message]
2019-02-06 11:07 ` [PATCH v3 1/3] firmware: xilinx: Add zynqmp_pm_get_chipid() API Nava kishore Manne
2019-02-06 11:07 ` [PATCH v3 2/3] dt-bindings: nvmem: Add bindings for ZynqMP nvmem driver Nava kishore Manne
2019-02-05 11:25 ` Srinivas Kandagatla
2019-02-06 11:07 ` [PATCH v3 3/3] nvmem: zynqmp: Added zynqmp nvmem firmware driver Nava kishore Manne
2019-02-05 11:24 ` Srinivas Kandagatla
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=a6c443e3-a9ba-ffa3-5f0f-69db6884646d@xilinx.com \
--to=michal.simek@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=nava.manne@xilinx.com \
--cc=rajanv@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®