From: Matthias Fuchs <matthias.fuchs@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] Added NAND flash pin configuration
Date: Fri, 10 Feb 2012 13:30:14 +0100 [thread overview]
Message-ID: <4F350DD6.8060507@esd.eu> (raw)
In-Reply-To: <1328633555-27538-5-git-send-email-robert@delien.nl>
Do you plan to post a patch to enable NAND on the EVK as well?
That shouldn't be a big deal.
Matthias
On 07.02.2012 17:52, robert at delien.nl wrote:
> From: Robert Delien <robert@delien.nl>
>
>
> Signed-off-by: Robert Delien <robert@delien.nl>
> ---
> board/freescale/mx28evk/iomux.c | 24 ++++++++++++++++++++++++
> 1 files changed, 24 insertions(+), 0 deletions(-)
>
> diff --git a/board/freescale/mx28evk/iomux.c b/board/freescale/mx28evk/iomux.c
> index d6f9d0a..781f36d 100644
> --- a/board/freescale/mx28evk/iomux.c
> +++ b/board/freescale/mx28evk/iomux.c
> @@ -29,6 +29,7 @@
> #define MUX_CONFIG_SSP1 (MXS_PAD_3V3 | MXS_PAD_8MA | MXS_PAD_PULLUP)
> #define MUX_CONFIG_ENET (MXS_PAD_3V3 | MXS_PAD_8MA | MXS_PAD_PULLUP)
> #define MUX_CONFIG_EMI (MXS_PAD_3V3 | MXS_PAD_12MA | MXS_PAD_NOPULL)
> +#define MUX_CONFIG_NAND (MXS_PAD_3V3 | MXS_PAD_4MA | MXS_PAD_NOPULL)
>
> const iomux_cfg_t iomux_setup[] = {
> /* Debug UART (DUART) */
> @@ -77,6 +78,29 @@ const iomux_cfg_t iomux_setup[] = {
> MX28_PAD_GPMI_ALE__GPIO_0_26 | MXS_PAD_3V3,
> MX28_PAD_GPMI_CE1N__GPIO_0_17 | MXS_PAD_3V3,
> MX28_PAD_GPMI_CE0N__GPIO_0_16 | MXS_PAD_3V3,
> +#else
> + /* On-board NAND flash ZIF-socket */
> + MX28_PAD_GPMI_D00__GPMI_D0 | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_D01__GPMI_D1 | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_D02__GPMI_D2 | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_D03__GPMI_D3 | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_D04__GPMI_D4 | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_D05__GPMI_D5 | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_D06__GPMI_D6 | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_D07__GPMI_D7 | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_RDN__GPMI_RDN |
> + MXS_PAD_1V8 | MXS_PAD_8MA | MXS_PAD_PULLUP,
> + MX28_PAD_GPMI_WRN__GPMI_WRN | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_ALE__GPMI_ALE | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_CLE__GPMI_CLE | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_RDY0__GPMI_READY0 | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_RDY1__GPMI_READY1 | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_CE0N__GPMI_CE0N | MUX_CONFIG_NAND,
> + MX28_PAD_GPMI_CE1N__GPMI_CE1N | MUX_CONFIG_NAND,
> + /* NAND Write-protect */
> + MX28_PAD_GPMI_RESETN__GPIO_0_28 | MXS_PAD_3V3,
> + /* Not used for NAND flash */
> + MX28_PAD_PWM4__GPIO_3_29 | MXS_PAD_3V3,
> #endif /* nCONFIG_CMD_NAND */
> /* FEC0 */
> MX28_PAD_ENET0_MDC__ENET0_MDC | MUX_CONFIG_ENET,
next prev parent reply other threads:[~2012-02-10 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 16:52 [U-Boot] [PATCH 0/4] i.MX28: Small correction to pin configuration robert at delien.nl
2012-02-07 16:52 ` [U-Boot] [PATCH 1/4] Debug UART pins configured to 3v3, instead of 1v8 robert at delien.nl
2012-02-07 16:52 ` [U-Boot] [PATCH 2/4] Correction to SSP0 drive strengths robert at delien.nl
2012-02-07 16:52 ` [U-Boot] [PATCH 3/4] SSP1 pins configured for MMC1 robert at delien.nl
2012-02-07 16:52 ` [U-Boot] [PATCH 4/4] Added NAND flash pin configuration robert at delien.nl
2012-02-07 17:28 ` Marek Vasut
2012-02-10 12:30 ` Matthias Fuchs [this message]
2012-02-10 12:42 ` Robert Deliën
2012-02-10 12:51 ` Matthias Fuchs
2012-02-10 12:53 ` Robert Deliën
2012-02-15 14:51 ` Robert Deliën
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=4F350DD6.8060507@esd.eu \
--to=matthias.fuchs@esd.eu \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox