From: Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@xilinx.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-gpio@vger.kernel.org>, <git@xilinx.com>,
<saikrishna12468@gmail.com>,
Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@xilinx.com>
Subject: [PATCH v2 0/3] Added ZynqMP pinctrl driver
Date: Tue, 19 Jan 2021 10:57:31 +0530 [thread overview]
Message-ID: <1611034054-63867-1-git-send-email-lakshmi.sai.krishna.potthuri@xilinx.com> (raw)
Added support for Xilinx ZynqMP pinctrl driver support and also
updated the Xilinx firmware driver to support pinctrl functionality.
This driver will query the pin information from the firmware and
allow configuring the pins as per the request.
changes in v2:
- Use pattern for pin names in yaml file.
- Updated to support multiple groups and pins.
- Added type ref for the vendor specific properties.
- Removed 'schmitt-cmos', instead used common properties.
- Removed macros for drive-strength property.
This might be resend for some people, as i had some trouble with my
email server earlier.
Sai Krishna Potthuri (3):
firmware: xilinx: Added pinctrl support
dt-bindings: pinctrl: Added binding for ZynqMP pinctrl driver
pinctrl: Added Xilinx ZynqMP pinctrl driver support
.../bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml | 337 ++++++
drivers/firmware/xilinx/zynqmp.c | 114 ++
drivers/pinctrl/Kconfig | 13 +
drivers/pinctrl/Makefile | 1 +
drivers/pinctrl/pinctrl-zynqmp.c | 1031 +++++++++++++++++
include/dt-bindings/pinctrl/pinctrl-zynqmp.h | 23 +
include/linux/firmware/xlnx-zynqmp.h | 90 ++
7 files changed, 1609 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml
create mode 100644 drivers/pinctrl/pinctrl-zynqmp.c
create mode 100644 include/dt-bindings/pinctrl/pinctrl-zynqmp.h
--
2.17.1
next reply other threads:[~2021-01-19 7:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 5:27 Sai Krishna Potthuri [this message]
2021-01-19 5:27 ` [PATCH v2 1/3] firmware: xilinx: Added pinctrl support Sai Krishna Potthuri
2021-01-22 12:50 ` Linus Walleij
2021-01-22 13:00 ` Michal Simek
2021-01-19 5:27 ` [PATCH v2 2/3] dt-bindings: pinctrl: Added binding for ZynqMP pinctrl driver Sai Krishna Potthuri
2021-02-09 2:20 ` Rob Herring
2021-02-09 8:16 ` Sai Krishna Potthuri
2021-02-09 13:56 ` Rob Herring
2021-02-09 14:58 ` Sai Krishna Potthuri
2021-01-19 5:27 ` [PATCH v2 3/3] pinctrl: Added Xilinx ZynqMP pinctrl driver support Sai Krishna Potthuri
2021-02-09 10:33 ` [PATCH v2 0/3] Added ZynqMP pinctrl driver Michael Walle
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=1611034054-63867-1-git-send-email-lakshmi.sai.krishna.potthuri@xilinx.com \
--to=lakshmi.sai.krishna.potthuri@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=saikrishna12468@gmail.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;
as well as URLs for NNTP newsgroup(s).