linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/6] arm: dts: vt8500: Update Wondermedia SoC dtsi files for pinctrl driver
Date: Tue, 12 Mar 2013 17:10:41 +1300	[thread overview]
Message-ID: <1363061441.23051.6.camel@gitbox> (raw)
In-Reply-To: <513E0A65.4000604@wwwdotorg.org>

On Mon, 2013-03-11 at 10:46 -0600, Stephen Warren wrote:
> On 03/08/2013 10:39 PM, Tony Prisk wrote:
> > This patch adds pinctrl nodes to the VIA VT8500 and Wondermedia SoC dtsi
> > files to support the pinctrl driver.
> 
> > diff --git a/arch/arm/boot/dts/vt8500.dtsi b/arch/arm/boot/dts/vt8500.dtsi
> 
> > +		pinctrl: pinctrl at d8110000 {
> > +			compatible = "via,vt8500-pinctrl";
> > +			gpio-controller;
> > +			reg = <0xd8110000 0x10000>;
> > +			#gpio-cells = <2>;
> > +			wm,pinmux = <0x00000001 0x00000001>;
> > +		};
> 
> In the binding documentation, "wm,pinmux" is listed under "optional
> sub-node properties", but here the property is included in the main
> node, not a sub-node.
> 
> I'm a little confused what this property means then...
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Sorry - this was copied in large part from the brcm,bcm2835-gpio.txt
binding. I added wm,pinmux alongside the existing wm,pins, wm,function
and wm,pull properties.

You are correct that this shouldn't be listed as a subnode property.

Regards
Tony P

  reply	other threads:[~2013-03-12  4:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09  5:39 [PATCH 0/6] arm: vt8500: Add support for pinctrl/gpio module Tony Prisk
2013-03-09  5:39 ` [PATCH 1/6] arm: vt8500: Increase available GPIOs on arch-vt8500 Tony Prisk
2013-03-11 16:38   ` Russell King - ARM Linux
2013-03-12  4:04     ` Tony Prisk
2013-03-09  5:39 ` [PATCH 2/6] pinctrl: gpio: vt8500: Add pincontrol driver for arch-vt8500 Tony Prisk
2013-03-11 16:44   ` Stephen Warren
2013-03-12  4:21     ` [Bulk] " Tony Prisk
2013-03-13 14:29       ` Linus Walleij
2013-03-13 19:08         ` Tony Prisk
2013-03-13 19:13           ` Linus Walleij
2013-03-14  5:59             ` Tony Prisk
2013-03-27  8:40               ` Linus Walleij
2013-03-13 16:11   ` Linus Walleij
2013-03-13 18:26     ` Stephen Warren
2013-03-13 18:52       ` Linus Walleij
2013-03-13 18:59         ` Tony Prisk
2013-03-13 19:00     ` Tony Prisk
2013-03-09  5:39 ` [PATCH 3/6] arm: dts: vt8500: Update Wondermedia SoC dtsi files for pinctrl driver Tony Prisk
2013-03-11 16:46   ` Stephen Warren
2013-03-12  4:10     ` Tony Prisk [this message]
2013-03-09  5:39 ` [PATCH 4/6] arm: vt8500: Remove gpio devicetree nodes Tony Prisk
2013-03-13 16:14   ` Linus Walleij
2013-03-13 16:26     ` Arnd Bergmann
2013-03-09  5:39 ` [PATCH 5/6] gpio: vt8500: Remove arch-vt8500 gpio driver Tony Prisk
2013-03-09  5:39 ` [PATCH 6/6] 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=1363061441.23051.6.camel@gitbox \
    --to=linux@prisktech.co.nz \
    --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;
as well as URLs for NNTP newsgroup(s).