linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nava kishore Manne <nava.manne@xilinx.com>
To: <robh+dt@kernel.org>, <mark.rutland@arm.com>,
	<michal.simek@xilinx.com>, <srinivas.kandagatla@linaro.org>,
	<nava.manne@xilinx.com>, <rajanv@xilinx.com>, <jollys@xilinx.com>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: [RFC PATCH v2 0/3] Add nvmem driver support for ZynqMP
Date: Tue, 4 Sep 2018 15:22:31 +0530	[thread overview]
Message-ID: <1536054754-3119-1-git-send-email-nava.manne@xilinx.com> (raw)

This series of patches are created On top of the
below series of patches.
https://lkml.org/lkml/2018/8/3/687

Nava kishore Manne (3):
  fairmware: xilinx: Add  zynqmp_pm_get_chipid() API
  dt-bindings: fpga: Add bindings for ZynqMP nvmem driver
  nvmem: zynqmp: Added zynqmp nvmem firmware driver

 .../firmware/xilinx/xlnx,zynqmp-firmware.txt       | 35 +++++++++
 drivers/firmware/xilinx/zynqmp.c                   | 24 +++++++
 drivers/nvmem/Kconfig                              | 10 +++
 drivers/nvmem/Makefile                             |  2 +
 drivers/nvmem/zynqmp_nvmem.c                       | 84 ++++++++++++++++++++++
 include/linux/firmware/xlnx-zynqmp.h               |  2 +
 6 files changed, 157 insertions(+)
 create mode 100644 drivers/nvmem/zynqmp_nvmem.c

-- 
2.7.4


             reply	other threads:[~2018-09-04  9:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04  9:52 Nava kishore Manne [this message]
2018-09-04  9:52 ` [RFC PATCH v2 1/3] fairmware: xilinx: Add zynqmp_pm_get_chipid() API Nava kishore Manne
2018-09-04  9:52 ` [RFC PATCH v2 2/3] dt-bindings: fpga: Add bindings for ZynqMP nvmem driver Nava kishore Manne
2018-09-16 14:10   ` Srinivas Kandagatla
2018-09-04  9:52 ` [RFC PATCH v2 3/3] nvmem: zynqmp: Added zynqmp nvmem firmware driver Nava kishore Manne
2018-09-16 14:10   ` Srinivas Kandagatla
2018-09-17  3:14     ` 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=1536054754-3119-1-git-send-email-nava.manne@xilinx.com \
    --to=nava.manne@xilinx.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=michal.simek@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;
as well as URLs for NNTP newsgroup(s).