Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1377445 > unrolled thread

[PATCH 0/4] Additional iProc GPIO support

Started byRay Jui <ray.jui@broadcom.com>
First post2016-04-13 02:30 +0200
Last post2016-04-14 16:40 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH 0/4] Additional iProc GPIO support Ray Jui <ray.jui@broadcom.com> - 2016-04-13 02:30 +0200
    [PATCH 3/4] dt-bindings: Update iProc GPIO bindings Ray Jui <ray.jui@broadcom.com> - 2016-04-13 02:30 +0200
      Re: [PATCH 3/4] dt-bindings: Update iProc GPIO bindings Rob Herring <robh@kernel.org> - 2016-04-14 16:40 +0200

#1377445 — [PATCH 0/4] Additional iProc GPIO support

FromRay Jui <ray.jui@broadcom.com>
Date2016-04-13 02:30 +0200
Subject[PATCH 0/4] Additional iProc GPIO support
Message-ID<rngHg-8eN-7@gated-at.bofh.it>
Add support to the iProc GPIO driver to allow PINCONF functions to be
disabled individually. Also add a new compatible string "brcm,iproc-gpio-only"
that allows this driver to be used as a pure GPIO driver without any PINCONF
functions enabled

Patch series is developed based on Linux v4.6-rc1 and available at:
https://github.com/Broadcom/cygnus-linux/tree/iproc-gpio-v1

Ray Jui (4):
  dt-bindings: Update iProc GPIO bindings
  pinctrl: iproc: Allow certain PINCONF functions to be disabled
  dt-bindings: Update iProc GPIO bindings
  pinctrl: iproc: Allow PINCONF to be disabled completely

 .../bindings/pinctrl/brcm,iproc-gpio.txt           |  12 ++-
 drivers/pinctrl/bcm/pinctrl-iproc-gpio.c           | 106 +++++++++++++++++++--
 include/dt-bindings/pinctrl/brcm,iproc-gpio.h      |  52 ++++++++++
 3 files changed, 162 insertions(+), 8 deletions(-)
 create mode 100644 include/dt-bindings/pinctrl/brcm,iproc-gpio.h

-- 
2.1.4

[toc] | [next] | [standalone]


#1377446 — [PATCH 3/4] dt-bindings: Update iProc GPIO bindings

FromRay Jui <ray.jui@broadcom.com>
Date2016-04-13 02:30 +0200
Subject[PATCH 3/4] dt-bindings: Update iProc GPIO bindings
Message-ID<rngQW-8jN-5@gated-at.bofh.it>
In reply to#1377445
Update the iProc GPIO binding document to introduce a new compatible
string "brcm,iproc-gpio-only", that allows the generic pinconf function
to be disabled completely

Signed-off-by: Ray Jui <ray.jui@broadcom.com>
Reviewed-by: Jon Mason <jon.mason@broadcom.com>
Reviewed-by: Scott Branden <scott.branden@broadcom.com>
---
 Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt b/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
index ddaa1b0..75a4370 100644
--- a/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
+++ b/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
@@ -3,8 +3,11 @@ 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"
+    For Cygnus, it must be brcm,cygnus-ccm-gpio", "brcm,cygnus-asiu-gpio", or
+"brcm,cygnus-crmu-gpio"
+    For non-Cygnus iProc SoCs, it must be either "brcm,iproc-gpio-only" (if
+only GPIO is supported) or "brcm,iproc-gpio" (if both generic pinconf and GPIO
+are supported)
 
 - reg:
     Define the base and range of the I/O address space that contains SoC
-- 
2.1.4

[toc] | [prev] | [next] | [standalone]


#1378934 — Re: [PATCH 3/4] dt-bindings: Update iProc GPIO bindings

FromRob Herring <robh@kernel.org>
Date2016-04-14 16:40 +0200
SubjectRe: [PATCH 3/4] dt-bindings: Update iProc GPIO bindings
Message-ID<rnQB4-33W-9@gated-at.bofh.it>
In reply to#1377446
On Tue, Apr 12, 2016 at 05:15:22PM -0700, Ray Jui wrote:
> Update the iProc GPIO binding document to introduce a new compatible
> string "brcm,iproc-gpio-only", that allows the generic pinconf function
> to be disabled completely
> 
> Signed-off-by: Ray Jui <ray.jui@broadcom.com>
> Reviewed-by: Jon Mason <jon.mason@broadcom.com>
> Reviewed-by: Scott Branden <scott.branden@broadcom.com>
> ---
>  Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt b/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
> index ddaa1b0..75a4370 100644
> --- a/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
> +++ b/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
> @@ -3,8 +3,11 @@ 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"
> +    For Cygnus, it must be brcm,cygnus-ccm-gpio", "brcm,cygnus-asiu-gpio", or
> +"brcm,cygnus-crmu-gpio"
> +    For non-Cygnus iProc SoCs, it must be either "brcm,iproc-gpio-only" (if
> +only GPIO is supported) or "brcm,iproc-gpio" (if both generic pinconf and GPIO
> +are supported)

No. That's not how compatible strings work. Use SoC specific compatible 
strings if you need to distinguish this.

Rob

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web