From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: imx50: add pinctrl support code for the IMX50 SoC
Date: Mon, 4 Nov 2013 14:06:08 +0100 [thread overview]
Message-ID: <20131104130608.GU24559@pengutronix.de> (raw)
In-Reply-To: <CACRpkdb5U2xBBVerbspTnW5=61kwx0+mvLGZF=VmdOKrN3QhHg@mail.gmail.com>
On Mon, Nov 04, 2013 at 01:14:32PM +0100, Linus Walleij wrote:
> On Tue, Oct 29, 2013 at 6:13 AM, <gerg@uclinux.org> wrote:
>
> > From: Greg Ungerer <gerg@uclinux.org>
> >
> > Add code to support the specific pin arrangements of the Freescale IMX50 SoC.
> >
> > Signed-off-by: Greg Ungerer <gerg@uclinux.org>
>
> Can I get some maintainer to review this for the next cycle?
>
> BTW: how many i.MX:es does remain? Have we not covered
> them all soon?
We have three different iomux ips. I once ordered them by an arbitrary
version number. We have
iomux-v1: i.MX1, i.MX21, i.MX27
iomux-v2: i.MX31
iomux-v3: i.MX25, i.MX35, i.MX50 i.MX51, i.MX53, i.MX6
I think it's quite unlikely that someone writes a iomux-v2 driver.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2013-11-04 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 5:13 [PATCH] pinctrl: imx50: add pinctrl support code for the IMX50 SoC gerg at uclinux.org
2013-11-04 12:14 ` Linus Walleij
2013-11-04 13:06 ` Sascha Hauer [this message]
2013-11-04 13:27 ` Shawn Guo
2013-11-05 9:54 ` Linus Walleij
2013-11-05 13:03 ` Greg Ungerer
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=20131104130608.GU24559@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).