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 v4 0/2] Additional iProc GPIO support
Date: Mon, 18 Jul 2016 10:20:16 -0700 [thread overview]
Message-ID: <1468862418-31477-1-git-send-email-ray.jui@broadcom.com> (raw)
Add support to the iProc GPIO driver for the NSP and Stingray iProc based SoCs.
The integration in NSP has drive strength pinconf feature disabled and the
integration in Stingray has all pinconf related features disabled and handled
by a different IP block
GITHUB repo: https://github.com/Broadcom/cygnus-linux.git
branch: iproc-gpio-v4
Changes from v3:
- Changed SoC specific compatible string name to have format of <soc>-<block>,
i.e., brcm,iproc-nsp-gpio and brcm,iproc-stingray-gpio, per suggestion from Rob
Changes from v2:
- Rebased to v4.7-rc1
- Changed to use SoC specific compatible string to handle SoC specific
changes in both NSP and Stingray
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"
Ray Jui (2):
dt-bindings: Update iProc GPIO bindings
pinctrl: iproc: Add NSP and Stingray GPIO support
.../bindings/pinctrl/brcm,iproc-gpio.txt | 18 +++-
drivers/pinctrl/bcm/pinctrl-iproc-gpio.c | 118 +++++++++++++++++++--
2 files changed, 127 insertions(+), 9 deletions(-)
--
2.1.4
next reply other threads:[~2016-07-18 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 17:20 Ray Jui [this message]
2016-07-18 17:20 ` [PATCH v4 1/2] dt-bindings: Update iProc GPIO bindings Ray Jui
2016-07-20 1:14 ` Rob Herring
2016-07-22 14:46 ` Linus Walleij
2016-07-18 17:20 ` [PATCH v4 2/2] pinctrl: iproc: Add NSP and Stingray GPIO support Ray Jui
2016-07-22 14:48 ` 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=1468862418-31477-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).