From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] pinctrl: pinctrl-single: pin names for pinctrl-single.bits
Date: Wed, 5 Jun 2013 15:02:05 -0700 [thread overview]
Message-ID: <20130605220204.GF3331@atomide.com> (raw)
In-Reply-To: <CAN1soZx+xYJT24XZqoynFJj3wjTuq14S6dtpd=SFw5_iDWTiWw@mail.gmail.com>
* Haojian Zhuang <haojian.zhuang@gmail.com> [130604 22:31]:
> On Tue, May 21, 2013 at 10:08 PM, Manjunathappa, Prakash
> <prakash.pm@ti.com> wrote:
> > Take care to name pin names as
> > register-offset.bit-pos-of-pin-in-register in case configuring multiple
> > pins in register.
> >
> > Signed-off-by: Manjunathappa, Prakash <prakash.pm@ti.com>
> > ---
>
> Acked-by: Haojian Zhuang <haojian.zhuang@gmail.com>
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2013-06-05 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 14:07 [PATCH 0/3] pinctrl: pinctrl-single: Add full fledge support to configure multiple pins of different modules Manjunathappa, Prakash
2013-05-21 14:08 ` [PATCH 1/3] pinctrl: pinctrl-single: enhance " Manjunathappa, Prakash
2013-06-05 5:24 ` Haojian Zhuang
2013-06-05 22:01 ` Tony Lindgren
2013-06-07 9:20 ` Linus Walleij
2013-05-21 14:08 ` [PATCH 2/3] pinctrl: pinctrl-single: pin names for pinctrl-single.bits Manjunathappa, Prakash
2013-06-05 5:25 ` Haojian Zhuang
2013-06-05 22:02 ` Tony Lindgren [this message]
2013-06-07 11:14 ` Linus Walleij
2013-05-21 14:08 ` [PATCH 3/3] ARM: davinci: da850: adopt to pinctrl-single driver to configure multiple pins Manjunathappa, Prakash
2013-06-24 11:48 ` Manjunathappa, Prakash
2013-06-24 14:52 ` Sekhar Nori
2013-05-24 9:03 ` [PATCH 0/3] pinctrl: pinctrl-single: Add full fledge support to configure multiple pins of different modules Linus Walleij
2013-05-26 16:11 ` Haojian Zhuang
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=20130605220204.GF3331@atomide.com \
--to=tony@atomide.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 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).