From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/4] ARM: add GPMI support for imx23/imx28
Date: Wed, 13 Apr 2011 15:51:52 +0200 [thread overview]
Message-ID: <20110413135152.GS18850@pengutronix.de> (raw)
In-Reply-To: <20110413114304.GA1897@S2100-06.ap.freescale.net>
Hi Shawn,
On Wed, Apr 13, 2011 at 07:43:05PM +0800, Shawn Guo wrote:
> On Wed, Apr 13, 2011 at 02:24:38PM +0800, Huang Shijie wrote:
> > + MX23_PAD_GPMI_D01__GPMI_D01 |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_D02__GPMI_D02 |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_D03__GPMI_D03 |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_D04__GPMI_D04 |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_D05__GPMI_D05 |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_D06__GPMI_D06 |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_D07__GPMI_D07 |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_CLE__GPMI_CLE |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_ALE__GPMI_ALE |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_WPN__GPMI_WPN |
> > + (MXS_PAD_12MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_WRN__GPMI_WRN |
> > + (MXS_PAD_12MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_RDN__GPMI_RDN |
> > + (MXS_PAD_12MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_RDY0__GPMI_RDY0 |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_RDY1__GPMI_RDY1 |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_CE0N__GPMI_CE0N |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > + MX23_PAD_GPMI_CE1N__GPMI_CE1N |
> > + (MXS_PAD_4MA | MXS_PAD_3V3 | MXS_PAD_NOPULL),
> > +
>
> mmc (ssp) has pin conflict with gpmi on both mx23evk and mx28evk.
hmm,
$ git grep GPMI linus/master -- arch/arm/mach-mxs/mach-mx23evk.c
linus/master:arch/arm/mach-mxs/mach-mx23evk.c: MX23_PAD_GPMI_D08__LCD_D18 | MXS
linus/master:arch/arm/mach-mxs/mach-mx23evk.c: MX23_PAD_GPMI_D09__LCD_D19 | MXS
linus/master:arch/arm/mach-mxs/mach-mx23evk.c: MX23_PAD_GPMI_D10__LCD_D20 | MXS
linus/master:arch/arm/mach-mxs/mach-mx23evk.c: MX23_PAD_GPMI_D11__LCD_D21 | MXS
linus/master:arch/arm/mach-mxs/mach-mx23evk.c: MX23_PAD_GPMI_D12__LCD_D22 | MXS
linus/master:arch/arm/mach-mxs/mach-mx23evk.c: MX23_PAD_GPMI_D13__LCD_D23 | MXS
linus/master:arch/arm/mach-mxs/mach-mx23evk.c: MX23_PAD_GPMI_D08__SSP1_DATA4 |
linus/master:arch/arm/mach-mxs/mach-mx23evk.c: MX23_PAD_GPMI_D09__SSP1_DATA5 |
linus/master:arch/arm/mach-mxs/mach-mx23evk.c: MX23_PAD_GPMI_D10__SSP1_DATA6 |
linus/master:arch/arm/mach-mxs/mach-mx23evk.c: MX23_PAD_GPMI_D11__SSP1_DATA7 |
so MX23_PAD_GPMI_D08 - MX23_PAD_GPMI_D13 is used (D08-D11 twice). So the
problem is already in linus/master. Is it that what you mean?
> How do you usually handle such pin conflicts on board?
I don't understand this question. Maybe: deciding which pad mux to use?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-04-13 13:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 6:24 [PATCH v5 0/4] add the GPMI controller driver for IMX23/IMX28 Huang Shijie
2011-04-13 6:24 ` [PATCH v5 3/4] MTD : add support for imx23 and imx28 Huang Shijie
2011-04-13 6:24 ` [PATCH v5 4/4] MTD : add GPMI driver in the config and Makefile Huang Shijie
2011-07-08 18:23 ` [PATCH v5 2/4] MTD : add the common code for GPMI controller driver Huang Shijie
2011-04-13 19:54 ` Lothar Waßmann
2011-04-14 2:20 ` Huang Shijie
2011-04-14 6:38 ` Lothar Waßmann
2011-04-14 6:40 ` Huang Shijie
2011-04-14 6:24 ` Lothar Waßmann
2011-04-14 6:36 ` Huang Shijie
2011-07-08 18:24 ` [PATCH v5 1/4] ARM: add GPMI support for imx23/imx28 Huang Shijie
2011-04-13 7:41 ` Lothar Waßmann
2011-04-13 9:42 ` Huang Shijie
2011-04-13 9:03 ` Uwe Kleine-König
2011-04-13 9:52 ` Huang Shijie
2011-04-13 10:03 ` Uwe Kleine-König
2011-04-13 10:49 ` Huang Shijie
2011-04-13 11:43 ` Shawn Guo
2011-04-13 13:25 ` Huang Shijie
2011-04-13 13:51 ` Uwe Kleine-König [this message]
2011-04-14 1:19 ` Shawn Guo
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=20110413135152.GS18850@pengutronix.de \
--to=u.kleine-koenig@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).