From: Dong Aisheng <aisheng.dong@freescale.com>
To: Dong Aisheng-B29396 <B29396@freescale.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linus.walleij@stericsson.com" <linus.walleij@stericsson.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
Guo Shawn-R65073 <r65073@freescale.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH 1/2] pinctrl: pinctrl-imx: add imx53 pinctrl driver
Date: Tue, 15 May 2012 14:44:03 +0800 [thread overview]
Message-ID: <20120515064401.GA10347@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <1337010369-28687-1-git-send-email-b29396@freescale.com>
On Mon, May 14, 2012 at 11:46:08PM +0800, Dong Aisheng-B29396 wrote:
> +See below for available PIN_FUNC_ID for imx53:
> +MX53_PAD_GPIO_19__KPP_COL_5 1
To align with mx6, the id base in the binding doc should start from 0.
Will update the doc in v2.
> +MX53_PAD_GPIO_19__GPIO4_5 2
> +MX53_PAD_GPIO_19__CCM_CLKO 3
> +MX53_PAD_GPIO_19__SPDIF_OUT1 4
> +MX53_PAD_GPIO_19__RTC_CE_RTC_EXT_TRIG2 5
> +MX53_PAD_GPIO_19__ECSPI1_RDY 6
...
Regards
Dong Aisheng
next prev parent reply other threads:[~2012-05-15 6:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 15:46 [PATCH 1/2] pinctrl: pinctrl-imx: add imx53 pinctrl driver Dong Aisheng
2012-05-14 15:46 ` [PATCH 2/2] pinctrl: pinctrl-imx: add imx51 " Dong Aisheng
2012-05-15 6:44 ` Dong Aisheng [this message]
2012-05-15 11:10 ` [PATCH 1/2] pinctrl: pinctrl-imx: add imx53 " Linus Walleij
2012-05-15 11:27 ` Dong Aisheng
2012-05-15 12:33 ` Linus Walleij
2012-05-15 13:05 ` Dong Aisheng
2012-05-16 2:13 ` Shawn Guo
2012-05-16 6:50 ` Linus Walleij
2012-05-16 7:57 ` Dong Aisheng
2012-05-16 7:59 ` Linus Walleij
2012-05-16 15:35 ` Shawn Guo
2012-05-16 6:53 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2012-05-15 7:49 Dong Aisheng
2012-05-16 7:45 ` Dong Aisheng
2012-05-16 7:49 ` Linus Walleij
2012-05-17 19:39 ` Stephen Warren
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=20120515064401.GA10347@shlinux2.ap.freescale.net \
--to=aisheng.dong@freescale.com \
--cc=B29396@freescale.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r65073@freescale.com \
--cc=s.hauer@pengutronix.de \
--cc=swarren@wwwdotorg.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).