From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 3/4] pinctrl: Add SPEAr3xx pinctrl drivers
Date: Mon, 16 Apr 2012 09:05:43 +0530 [thread overview]
Message-ID: <4F8B938F.2000903@st.com> (raw)
In-Reply-To: <4F8850AB.3090109@wwwdotorg.org>
On 4/13/2012 9:43 PM, Stephen Warren wrote:
> 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.
Ok.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@st.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "devicetree-discuss@ozlabs.org" <devicetree-discuss@ozlabs.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
spear-devel <spear-devel@list.st.com>,
"viresh.linux@gmail.com" <viresh.linux@gmail.com>,
"olof@lixom.net" <olof@lixom.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V3 3/4] pinctrl: Add SPEAr3xx pinctrl drivers
Date: Mon, 16 Apr 2012 09:05:43 +0530 [thread overview]
Message-ID: <4F8B938F.2000903@st.com> (raw)
In-Reply-To: <4F8850AB.3090109@wwwdotorg.org>
On 4/13/2012 9:43 PM, Stephen Warren wrote:
> 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.
Ok.
--
viresh
next prev parent reply other threads:[~2012-04-16 3:35 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
2012-04-13 16:13 ` Stephen Warren
2012-04-16 3:35 ` Viresh Kumar [this message]
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=4F8B938F.2000903@st.com \
--to=viresh.kumar@st.com \
--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.