Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932676AbbLGO5S (ORCPT ); Mon, 7 Dec 2015 09:57:18 -0500 Received: from mail.kernel.org ([198.145.29.136]:42060 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932314AbbLGO5P (ORCPT ); Mon, 7 Dec 2015 09:57:15 -0500 Date: Mon, 7 Dec 2015 08:57:10 -0600 From: Rob Herring To: Yendapally Reddy Dhananjaya Reddy Cc: Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Ray Jui , Scott Branden , Jon Mason , Linus Walleij , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, bcm-kernel-feedback-list@broadcom.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/3] pinctrl: Broadcom NSP GPIO-a device tree bindings Message-ID: <20151207145710.GA14994@rob-hp-laptop> References: <1449249057-12975-1-git-send-email-yrdreddy@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1449249057-12975-1-git-send-email-yrdreddy@broadcom.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3245 Lines: 106 On Fri, Dec 04, 2015 at 12:10:57PM -0500, Yendapally Reddy Dhananjaya Reddy wrote: > Device tree binding documentation for Broadcom NSP GPIO-a > > Signed-off-by: Yendapally Reddy Dhananjaya Reddy Acked-by: Rob Herring > --- > .../devicetree/bindings/pinctrl/brcm,nsp-gpio.txt | 80 ++++++++++++++++++++++ > 1 file changed, 80 insertions(+) > create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,nsp-gpio.txt > > diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,nsp-gpio.txt b/Documentation/devicetree/bindings/pinctrl/brcm,nsp-gpio.txt > new file mode 100644 > index 0000000..0844168 > --- /dev/null > +++ b/Documentation/devicetree/bindings/pinctrl/brcm,nsp-gpio.txt > @@ -0,0 +1,80 @@ > +Broadcom Northstar plus (NSP) GPIO/PINCONF Controller > + > +Required properties: > +- compatible: > + Must be "brcm,nsp-gpio-a" > + > +- reg: > + Should contain the register physical address and length for each of > + GPIO base, IO control registers > + > +- #gpio-cells: > + Must be two. The first cell is the GPIO pin number (within the > + controller's pin space) and the second cell is used for the following: > + bit[0]: polarity (0 for active high and 1 for active low) > + > +- gpio-controller: > + Specifies that the node is a GPIO controller > + > +- ngpios: > + Number of gpios supported (58x25 supports 32 and 58x23 supports 24) > + > +Optional properties: > +- interrupts: > + Interrupt ID > + > +- interrupt-controller: > + Specifies that the node is an interrupt controller > + > +- gpio-ranges: > + Specifies the mapping between gpio controller and pin-controllers pins. > + This requires 4 fields in cells defined as - > + 1. Phandle of pin-controller. > + 2. GPIO base pin offset. > + 3 Pin-control base pin offset. > + 4. number of gpio pins which are linearly mapped from pin base. > + > +Supported generic PINCONF properties in child nodes: > +- pins: > + The list of pins (within the controller's own pin space) that properties > + in the node apply to. Pin names are "gpio-" > + > +- bias-disable: > + Disable pin bias > + > +- bias-pull-up: > + Enable internal pull up resistor > + > +- bias-pull-down: > + Enable internal pull down resistor > + > +- drive-strength: > + Valid drive strength values include 2, 4, 6, 8, 10, 12, 14, 16 (mA) > + > +Example: > + > + gpioa: gpio@18000020 { > + compatible = "brcm,nsp-gpio-a"; > + reg = <0x18000020 0x100>, > + <0x1803f1c4 0x1c>; > + #gpio-cells = <2>; > + gpio-controller; > + ngpios = <32>; > + gpio-ranges = <&pinctrl 0 0 31>; > + interrupt-controller; > + interrupts = ; > + > + /* Hog a few default settings */ > + pinctrl-names = "default"; > + pinctrl-0 = <&led>; > + led: led { > + pins = "gpio-1"; > + bias-pull-up; > + }; > + > + pwr: pwr { > + gpio-hog; > + gpios = <3 1>; > + output-high; > + }; > + }; > -- > 2.1.0 > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/