From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 3/7] pinctrl: gpio: vt8500: Add pincontrol driver for arch-vt8500
Date: Mon, 25 Mar 2013 11:05:15 -0600 [thread overview]
Message-ID: <515083CB.1060908@wwwdotorg.org> (raw)
In-Reply-To: <1364015633-18580-4-git-send-email-linux@prisktech.co.nz>
On 03/22/2013 11:13 PM, Tony Prisk wrote:
> This patch adds support for the GPIO/pinmux controller found on the VIA
> VT8500 and Wondermedia WM8xxx-series SoCs.
>
> Each pin within the controller is capable of operating as a GPIO or as
> an alternate function. The pins are numbered according to their control
> bank/bit so that if new pins are added, the existing numbering is maintained.
>
> All currently supported SoCs are included: VT8500, WM8505, WM8650, WM8750 and
> WM8850.
> diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-vt8500.txt b/Documentation/devicetree/bindings/pinctrl/pinctrl-vt8500.txt
> +Required properties:
> +- gpio-controller: Marks the device node as a GPIO controller.
> +- #gpio-cells : Should be two. The first cell is the pin number and the
> + second cell is used to specify optional parameters.
What are those optional parameters? This binding should define them.
> +Optional properties:
> +- wm,pinmux: A value and mask pair describing the configuration changes to
> + the pinmux register. Only bits marked 1 in the mask will be changed.
This needs more explanation. What does this do and why is it needed?
Other than that, this binding looks fine.
next prev parent reply other threads:[~2013-03-25 17:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 5:13 [PATCHv2 0/7] arm: vt8500: Add support for pinctrl/gpio module Tony Prisk
2013-03-23 5:13 ` [PATCHv2 1/7] of: Add support for reading a u32 from a multi-value property Tony Prisk
2013-03-23 5:13 ` Tony Prisk
2013-04-15 10:12 ` Grant Likely
2013-04-15 10:12 ` Grant Likely
2013-03-23 5:13 ` [PATCHv2 2/7] arm: vt8500: Increase available GPIOs on arch-vt8500 Tony Prisk
2013-03-23 10:44 ` Russell King - ARM Linux
2013-03-23 18:04 ` Tony Prisk
2013-03-23 5:13 ` [PATCHv2 3/7] pinctrl: gpio: vt8500: Add pincontrol driver for arch-vt8500 Tony Prisk
2013-03-25 17:05 ` Stephen Warren [this message]
2013-03-25 18:51 ` Tony Prisk
2013-03-26 20:28 ` Stephen Warren
2013-03-27 4:59 ` Tony Prisk
2013-03-27 16:47 ` Stephen Warren
2013-03-27 9:23 ` Tony Prisk
2013-03-27 15:53 ` Stephen Warren
2013-03-28 5:03 ` Tony Prisk
2013-03-23 5:13 ` [PATCHv2 4/7] arm: dts: vt8500: Update Wondermedia SoC dtsi files for pinctrl driver Tony Prisk
2013-03-23 5:13 ` [PATCHv2 5/7] arm: vt8500: Remove gpio devicetree nodes Tony Prisk
2013-03-23 5:13 ` [PATCHv2 6/7] gpio: vt8500: Remove arch-vt8500 gpio driver Tony Prisk
2013-03-23 5:13 ` [PATCHv2 7/7] arm: vt8500: Remove pinmux configuration from mach-vt8500/vt8500.c Tony Prisk
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=515083CB.1060908@wwwdotorg.org \
--to=swarren@wwwdotorg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.