From: Rob Herring <robh@kernel.org>
To: Ray Jui <ray.jui@broadcom.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: Update iProc GPIO bindings
Date: Sat, 16 Jul 2016 16:20:28 -0500 [thread overview]
Message-ID: <20160716212028.GA6320@rob-hp-laptop> (raw)
In-Reply-To: <1468345158-17676-2-git-send-email-ray.jui@broadcom.com>
On Tue, Jul 12, 2016 at 10:39:17AM -0700, Ray Jui wrote:
> Update the iProc GPIO binding document to add new compatible strings
> "brcm,iproc-gpio-nsp" and "brcm,iproc-gpio-stingray" to support the
> iProc based GPIO controller used in the NSP and Stingray SoCs,
> respectively
>
> Signed-off-by: Ray Jui <ray.jui@broadcom.com>
> ---
> .../devicetree/bindings/pinctrl/brcm,iproc-gpio.txt | 18 ++++++++++++++++--
> 1 file changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt b/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
> index e427792..7bd1614 100644
> --- a/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
> +++ b/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
> @@ -3,8 +3,22 @@ Broadcom iProc GPIO/PINCONF Controller
> Required properties:
>
> - compatible:
> - Must be "brcm,cygnus-ccm-gpio", "brcm,cygnus-asiu-gpio",
> - "brcm,cygnus-crmu-gpio" or "brcm,iproc-gpio"
> + "brcm,iproc-gpio" for the generic iProc based GPIO controller IP that
> + supports full-featured pinctrl and GPIO functions used in various iProc
> + based SoCs
> +
> + May contain an SoC-specific compatibility string to accommodate any
> + SoC-specific features
> +
> + "brcm,cygnus-ccm-gpio", "brcm,cygnus-asiu-gpio", or
> + "brcm,cygnus-crmu-gpio" for Cygnus SoCs
> +
> + "brcm,iproc-gpio-nsp" for the iProc NSP SoC that has drive strength support
> + disabled
The typical ordering is <soc>-<block>, so:
iproc-nsp-gpio
> +
> + "brcm,iproc-gpio-stingray" for the iProc Stingray SoC that has the general
> + pinctrl support completely disabled in this IP block. In Stingray, a
> + different IP block is used to handle pinctrl related functions
iproc-stingray-gpio
>
> - reg:
> Define the base and range of the I/O address space that contains SoC
> --
> 2.1.4
>
next prev parent reply other threads:[~2016-07-16 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 17:39 [PATCH v3 0/2] Additional iProc GPIO support Ray Jui
2016-07-12 17:39 ` [PATCH v3 1/2] dt-bindings: Update iProc GPIO bindings Ray Jui
2016-07-16 21:20 ` Rob Herring [this message]
2016-07-18 16:34 ` Ray Jui
2016-07-12 17:39 ` [PATCH v3 2/2] pinctrl: iproc: Add NSP and Stingray GPIO support Ray Jui
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=20160716212028.GA6320@rob-hp-laptop \
--to=robh@kernel.org \
--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=ray.jui@broadcom.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).