From: Dong Aisheng-B29396 <B29396@freescale.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Sascha Hauer <s.hauer@pengutronix.de>
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>,
Guo Shawn-R65073 <r65073@freescale.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: RE: [RFC PATCH 2/3] pinctrl: imx: add pinmux-imx53 support
Date: Tue, 6 Dec 2011 03:42:11 +0000 [thread overview]
Message-ID: <65EE16ACC360FA4D99C96DC085B3F7723457FD@039-SN1MPN1-002.039d.mgd.msft.net> (raw)
In-Reply-To: <CACRpkdZ0aNj-BsdtD2R-bEWQfMzsOMNbdh6ryVtgwET3Ry7xXA@mail.gmail.com>
> -----Original Message-----
> From: Linus Walleij [mailto:linus.walleij@linaro.org]
> Sent: Tuesday, December 06, 2011 1:01 AM
> To: Sascha Hauer
> Cc: Dong Aisheng-B29396; linux-kernel@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; linus.walleij@stericsson.com; Guo Shawn-
> R65073; kernel@pengutronix.de
> Subject: Re: [RFC PATCH 2/3] pinctrl: imx: add pinmux-imx53 support
>
> On Sun, Dec 4, 2011 at 5:11 PM, Sascha Hauer <s.hauer@pengutronix.de>
> wrote:
>
> > I don't think that this grouping of pads to their functions makes
> > sense. On i.MX every pad is muxed independently and not in groups.
> > Which pins belong to which function is board specific and not SoC
> > specific.
>
> True, Dong can this be moved to the imx pinctrl platform data and passed
> in from arch/arm/[plat|mach]-* board files instead?
> That is probably where it belongs today.
>
Yes, I will do that.
> I know that this data is in drivers/pinctrl for the U300 and SIRF, but
> that is because they only have one single board variant.
>
> Yours,
> Linus Walleij
Regards
Dong Aisheng
WARNING: multiple messages have this Message-ID (diff)
From: B29396@freescale.com (Dong Aisheng-B29396)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/3] pinctrl: imx: add pinmux-imx53 support
Date: Tue, 6 Dec 2011 03:42:11 +0000 [thread overview]
Message-ID: <65EE16ACC360FA4D99C96DC085B3F7723457FD@039-SN1MPN1-002.039d.mgd.msft.net> (raw)
In-Reply-To: <CACRpkdZ0aNj-BsdtD2R-bEWQfMzsOMNbdh6ryVtgwET3Ry7xXA@mail.gmail.com>
> -----Original Message-----
> From: Linus Walleij [mailto:linus.walleij at linaro.org]
> Sent: Tuesday, December 06, 2011 1:01 AM
> To: Sascha Hauer
> Cc: Dong Aisheng-B29396; linux-kernel at vger.kernel.org; linux-arm-
> kernel at lists.infradead.org; linus.walleij at stericsson.com; Guo Shawn-
> R65073; kernel at pengutronix.de
> Subject: Re: [RFC PATCH 2/3] pinctrl: imx: add pinmux-imx53 support
>
> On Sun, Dec 4, 2011 at 5:11 PM, Sascha Hauer <s.hauer@pengutronix.de>
> wrote:
>
> > I don't think that this grouping of pads to their functions makes
> > sense. On i.MX every pad is muxed independently and not in groups.
> > Which pins belong to which function is board specific and not SoC
> > specific.
>
> True, Dong can this be moved to the imx pinctrl platform data and passed
> in from arch/arm/[plat|mach]-* board files instead?
> That is probably where it belongs today.
>
Yes, I will do that.
> I know that this data is in drivers/pinctrl for the U300 and SIRF, but
> that is because they only have one single board variant.
>
> Yours,
> Linus Walleij
Regards
Dong Aisheng
next prev parent reply other threads:[~2011-12-06 3:42 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 11:49 [RFC PATCH 1/3] pinctrl: imx: add pinmux imx core driver Dong Aisheng
2011-12-04 11:49 ` Dong Aisheng
2011-12-04 11:49 ` [RFC PATCH 2/3] pinctrl: imx: add pinmux-imx53 support Dong Aisheng
2011-12-04 11:49 ` Dong Aisheng
2011-12-04 16:11 ` Sascha Hauer
2011-12-04 16:11 ` Sascha Hauer
2011-12-05 2:43 ` Dong Aisheng
2011-12-05 2:43 ` Dong Aisheng
2011-12-05 7:51 ` Sascha Hauer
2011-12-05 7:51 ` Sascha Hauer
2011-12-06 3:21 ` Dong Aisheng-B29396
2011-12-06 3:21 ` Dong Aisheng-B29396
2011-12-05 17:03 ` Linus Walleij
2011-12-05 17:03 ` Linus Walleij
2011-12-05 17:01 ` Linus Walleij
2011-12-05 17:01 ` Linus Walleij
2011-12-06 3:42 ` Dong Aisheng-B29396 [this message]
2011-12-06 3:42 ` Dong Aisheng-B29396
2011-12-05 16:57 ` Linus Walleij
2011-12-05 16:57 ` Linus Walleij
2011-12-05 21:18 ` Sascha Hauer
2011-12-05 21:18 ` Sascha Hauer
2011-12-06 5:54 ` Dong Aisheng-B29396
2011-12-06 5:54 ` Dong Aisheng-B29396
2011-12-06 6:58 ` Shawn Guo
2011-12-06 6:58 ` Shawn Guo
2011-12-06 7:21 ` Dong Aisheng-B29396
2011-12-06 7:21 ` Dong Aisheng-B29396
2011-12-06 6:25 ` Shawn Guo
2011-12-06 6:25 ` Shawn Guo
2011-12-06 7:33 ` Lothar Waßmann
2011-12-06 7:33 ` Lothar Waßmann
2011-12-06 8:00 ` Shawn Guo
2011-12-06 8:00 ` Shawn Guo
2011-12-06 8:05 ` Uwe Kleine-König
2011-12-06 8:05 ` Uwe Kleine-König
2011-12-07 9:01 ` Linus Walleij
2011-12-07 9:01 ` Linus Walleij
2011-12-06 10:53 ` Sascha Hauer
2011-12-06 10:53 ` Sascha Hauer
2011-12-06 3:39 ` Dong Aisheng
2011-12-06 3:39 ` Dong Aisheng
2011-12-04 11:49 ` [RFC PATCH 3/3] pinctrl: imx: add pinmux-imx6q support Dong Aisheng
2011-12-04 11:49 ` Dong Aisheng
2011-12-06 7:23 ` Shawn Guo
2011-12-06 7:23 ` Shawn Guo
2011-12-06 7:23 ` Dong Aisheng-B29396
2011-12-06 7:23 ` Dong Aisheng-B29396
2011-12-06 14:44 ` Shawn Guo
2011-12-06 14:44 ` Shawn Guo
2011-12-07 9:09 ` Linus Walleij
2011-12-07 9:09 ` Linus Walleij
2011-12-07 9:18 ` Dong Aisheng-B29396
2011-12-07 9:18 ` Dong Aisheng-B29396
2011-12-05 13:09 ` [RFC PATCH 1/3] pinctrl: imx: add pinmux imx core driver Linus Walleij
2011-12-05 13:09 ` Linus Walleij
2011-12-06 3:41 ` Dong Aisheng-B29396
2011-12-06 3:41 ` Dong Aisheng-B29396
2011-12-06 7:06 ` Shawn Guo
2011-12-06 7:06 ` Shawn Guo
2011-12-06 7:13 ` Dong Aisheng-B29396
2011-12-06 7:13 ` Dong Aisheng-B29396
2011-12-06 7:32 ` Shawn Guo
2011-12-06 7:32 ` Shawn Guo
2011-12-06 7:39 ` Shawn Guo
2011-12-06 7:39 ` Shawn Guo
2011-12-06 7:35 ` Dong Aisheng-B29396
2011-12-06 7:35 ` Dong Aisheng-B29396
2011-12-06 9:42 ` Shawn Guo
2011-12-06 9:42 ` Shawn Guo
2011-12-06 9:38 ` Dong Aisheng-B29396
2011-12-06 9:38 ` Dong Aisheng-B29396
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=65EE16ACC360FA4D99C96DC085B3F7723457FD@039-SN1MPN1-002.039d.mgd.msft.net \
--to=b29396@freescale.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--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 \
/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.