From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 3/4] pinctrl: Add SPEAr3xx pinctrl drivers
Date: Fri, 13 Apr 2012 10:13:31 -0600 [thread overview]
Message-ID: <4F8850AB.3090109@wwwdotorg.org> (raw)
In-Reply-To: <61fe5fe87fdddfc66d21d82b1039de3782b50201.1334207964.git.viresh.kumar@st.com>
On 04/11/2012 11:24 PM, Viresh Kumar wrote:
> This adds pinctrl driver for SPEAr3xx family. SPEAr3xx family supports three
> families: SPEAr300, SPEAr310 and SPEAr320.
> +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl_spear.txt
> +Required subnode-properties:
> +- st,pins : An array of strings. Each string contains the name of a pin or
> + group.
> +- st,function: A string containing the name of the function to mux to the pin or
> + group. See the SPEAr's TRM to determine which are valid for each pin or group.
> +
> + Valid values for group and function names can be found from looking at the
> + group and function arrays in driver files:
> + drivers/pinctrl/spear/pinctrl-spear3*0.c
It might be nice to enumerate the pin/group/function names here, but if
they're identical to the TRM I guess it's fine not to.
Looking at the Tegra binding docs, I see I forgot to enumerate the
function names although I did enumerate everything else.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org,
viresh.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH V3 3/4] pinctrl: Add SPEAr3xx pinctrl drivers
Date: Fri, 13 Apr 2012 10:13:31 -0600 [thread overview]
Message-ID: <4F8850AB.3090109@wwwdotorg.org> (raw)
In-Reply-To: <61fe5fe87fdddfc66d21d82b1039de3782b50201.1334207964.git.viresh.kumar-qxv4g6HH51o@public.gmane.org>
On 04/11/2012 11:24 PM, Viresh Kumar wrote:
> This adds pinctrl driver for SPEAr3xx family. SPEAr3xx family supports three
> families: SPEAr300, SPEAr310 and SPEAr320.
> +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl_spear.txt
> +Required subnode-properties:
> +- st,pins : An array of strings. Each string contains the name of a pin or
> + group.
> +- st,function: A string containing the name of the function to mux to the pin or
> + group. See the SPEAr's TRM to determine which are valid for each pin or group.
> +
> + Valid values for group and function names can be found from looking at the
> + group and function arrays in driver files:
> + drivers/pinctrl/spear/pinctrl-spear3*0.c
It might be nice to enumerate the pin/group/function names here, but if
they're identical to the TRM I guess it's fine not to.
Looking at the Tegra binding docs, I see I forgot to enumerate the
function names although I did enumerate everything else.
next prev parent reply other threads:[~2012-04-13 16:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 5:24 [PATCH V3 0/4] pinctrl: Add SPEAr pinctrl support Viresh Kumar
2012-04-12 5:24 ` Viresh Kumar
2012-04-12 5:24 ` [PATCH V3 1/4] SPEAr: Remove existing padmux support for SPEAr Viresh Kumar
2012-04-12 5:24 ` Viresh Kumar
2012-04-13 13:00 ` Linus Walleij
2012-04-13 13:00 ` Linus Walleij
2012-04-12 5:24 ` [PATCH V3 2/4] pinctrl: Add SPEAr pinctrl drivers Viresh Kumar
2012-04-12 5:24 ` Viresh Kumar
2012-04-13 13:01 ` Linus Walleij
2012-04-13 13:01 ` Linus Walleij
2012-04-13 16:08 ` Stephen Warren
2012-04-13 16:08 ` Stephen Warren
2012-04-16 3:35 ` Viresh Kumar
2012-04-16 3:35 ` Viresh Kumar
2012-04-12 5:24 ` [PATCH V3 4/4] SPEAr3xx: Add pinctrl support for boards Viresh Kumar
2012-04-12 5:24 ` Viresh Kumar
2012-04-13 13:05 ` Linus Walleij
2012-04-13 13:05 ` Linus Walleij
2012-04-13 16:18 ` Stephen Warren
2012-04-13 16:18 ` Stephen Warren
2012-04-16 3:37 ` Viresh Kumar
2012-04-16 3:37 ` Viresh Kumar
2012-04-16 18:05 ` Stephen Warren
2012-04-16 18:05 ` Stephen Warren
[not found] ` <4F8C5F68.7070105-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-04-16 18:08 ` viresh kumar
[not found] ` <61fe5fe87fdddfc66d21d82b1039de3782b50201.1334207964.git.viresh.kumar@st.com>
2012-04-13 13:04 ` [PATCH V3 3/4] pinctrl: Add SPEAr3xx pinctrl drivers Linus Walleij
2012-04-13 13:04 ` Linus Walleij
2012-04-13 16:13 ` Stephen Warren [this message]
2012-04-13 16:13 ` Stephen Warren
2012-04-16 3:35 ` Viresh Kumar
2012-04-16 3:35 ` Viresh Kumar
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=4F8850AB.3090109@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.