From: Ray Jui <ray.jui@broadcom.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, Ray Jui <ray.jui@broadcom.com>
Subject: [PATCH v2 0/2] Additional iProc GPIO support
Date: Mon, 2 May 2016 13:51:46 -0700 [thread overview]
Message-ID: <1462222308-4869-1-git-send-email-ray.jui@broadcom.com> (raw)
Add support to the iProc GPIO driver for v2 and v3 revisions of the iProc GPIO
controllers. The v2 revision is used on NSP with drive strength pinconf
feature disabled and the v3 revision is used on Stingray with all pinconf
features disabled
Changes from v1:
- Changed to use compatible strings "brcm,iproc-gpio-v2" and
"brcm,iproc-gpio-v3" to deal with differences among various iProc based SoCs
- Removed DT header "include/dt-bindings/pinctrl/brcm,iproc-gpio.h"
Patch series is developed based on Linux v4.6-rc1 and available at:
https://github.com/Broadcom/cygnus-linux/tree/iproc-gpio-v2
Ray Jui (2):
dt-bindings: Update iProc GPIO bindings
pinctrl: iproc: Add v2/v3 GPIO support
.../bindings/pinctrl/brcm,iproc-gpio.txt | 11 +-
drivers/pinctrl/bcm/pinctrl-iproc-gpio.c | 115 +++++++++++++++++++--
2 files changed, 119 insertions(+), 7 deletions(-)
--
2.1.4
next reply other threads:[~2016-05-02 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 20:51 Ray Jui [this message]
2016-05-02 20:51 ` [PATCH v2 1/2] dt-bindings: Update iProc GPIO bindings Ray Jui
2016-05-04 13:20 ` Rob Herring
2016-05-04 16:29 ` Ray Jui
2016-05-11 14:06 ` Rob Herring
2016-05-11 15:50 ` Ray Jui
2016-05-02 20:51 ` [PATCH v2 2/2] pinctrl: iproc: Add v2/v3 GPIO support Ray Jui
2016-05-11 9:29 ` [PATCH v2 0/2] Additional iProc " Linus Walleij
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=1462222308-4869-1-git-send-email-ray.jui@broadcom.com \
--to=ray.jui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).