public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] pinctrl: Broadcom NSP pinctrl device tree bindings
Date: Sun, 22 Nov 2015 14:45:53 -0600	[thread overview]
Message-ID: <20151122204553.GA31160@rob-hp-laptop> (raw)
In-Reply-To: <1448042191-1982-1-git-send-email-yrdreddy@broadcom.com>

On Fri, Nov 20, 2015 at 12:56:31PM -0500, Yendapally Reddy Dhananjaya Reddy wrote:
> Device tree binding documentation for Broadcom NSP IOMUX driver
> 
> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yrdreddy@broadcom.com>

Acked-by: Rob Herring <robh@kernel.org>

> ---
>  .../bindings/pinctrl/brcm,nsp-pinmux.txt           | 79 ++++++++++++++++++++++
>  1 file changed, 79 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,nsp-pinmux.txt
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,nsp-pinmux.txt b/Documentation/devicetree/bindings/pinctrl/brcm,nsp-pinmux.txt
> new file mode 100644
> index 0000000..603564e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/brcm,nsp-pinmux.txt
> @@ -0,0 +1,79 @@
> +Broadcom NSP (Northstar plus) IOMUX Controller
> +
> +The NSP IOMUX controller supports group based mux configuration. In
> +addition, certain pins can be muxed to GPIO function individually.
> +
> +Required properties:
> +- compatible:
> +    Must be "brcm,nsp-pinmux"
> +
> +- reg:
> +    Should contain the register physical address and length for each of
> +    GPIO_CONTROL0, GP_AUX_SEL and IPROC_CONFIG IOMUX registers
> +
> +Properties in subnodes:
> +- function:
> +    The mux function to select
> +
> +- groups:
> +    The list of groups to select with a given function
> +
> +For more details, refer to
> +Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
> +
> +For example:
> +
> +	pinmux: pinmux at 1803f1c0 {
> +		compatible = "brcm,nsp-pinmux";
> +		reg = <0x1803f1c0 0x04>,
> +		      <0x18030028 0x04>,
> +		      <0x1803f408 0x04>;
> +
> +		pinctrl-names = "default";
> +		pinctrl-0 = <&pwm &gpio_b &nand_sel>;
> +
> +		pwm: pwm {
> +			function = "pwm";
> +			groups = "pwm0_grp", "pwm1_grp";
> +		};
> +
> +		gpio_b: gpio_b {
> +			function = "gpio_b";
> +			groups = "gpio_b_0_grp", "gpio_b_1_grp";
> +		};
> +
> +		nand_sel: nand_sel {
> +			function = "nand";
> +			groups = "nand_grp";
> +		};
> +	};
> +
> +List of supported functions and groups in Northstar Plus:
> +
> +"spi": "spi_grp"
> +
> +"i2c": "i2c_grp"
> +
> +"mdio": "mdio_grp"
> +
> +"pwm": "pwm0_grp", "pwm1_grp", "pwm2_grp", "pwm3_grp"
> +
> +"gpio_b": "gpio_b_0_grp", "gpio_b_1_grp", "gpio_b_2_grp", "gpio_b_3_grp"
> +
> +"uart1": "uart1_grp"
> +
> +"uart2": "uart2_grp"
> +
> +"synce": "synce_grp"
> +
> +"sata_led_grps": "sata0_led_grp", "sata1_led_grp"
> +
> +"xtal_out": "xtal_out_grp"
> +
> +"sdio": "sdio_pwr_grp", "sdio_1p8v_grp"
> +
> +"switch_led": "switch_p05_led0_grp", "switch_p05_led1_grp"
> +
> +"nand": "nand_grp"
> +
> +"emmc": "emmc_grp"
> -- 
> 2.1.0
> 

      reply	other threads:[~2015-11-22 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 17:56 [PATCH 1/3] pinctrl: Broadcom NSP pinctrl device tree bindings Yendapally Reddy Dhananjaya Reddy
2015-11-22 20:45 ` Rob Herring [this message]

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=20151122204553.GA31160@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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