From: stefano babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Correct corrupted NAND Flash access on KARO TX25 modules
Date: Sun, 01 Apr 2012 12:33:08 +0200 [thread overview]
Message-ID: <4F782EE4.7030407@denx.de> (raw)
In-Reply-To: <7605B15734F74B40A124AED46B25250A4F257F@HEFRMBX01.sofr.hefr.lan>
Am 31/03/2012 09:31, schrieb Gachet Daniel:
> This short patch correct corrupted data while reading NAND flash modules on the KARO TX25 module.
>
> The current version of the mxc_nand driver uses the symmetric mode to access the NAND flash, but the devices populated on the KARO TX25 only support an asymmetric mode (i.MX25: bit 8 within NAND_FLASH_CONFIG1 register cleared).
>
> Signed-off-by: Daniel Gachet <daniel.gachet@hefr.ch>
> Cc: Wolfgang Denk <wd@denx.de >
>
> diff -upr drivers/mtd/nand/mxc_nand.c drivers/mtd/nand/mxc_nand.c
> --- drivers/mtd/nand/mxc_nand.c 2011-12-23 20:25:35.000000000 +0100
> +++ drivers/mtd/nand/mxc_nand.c 2012-03-30 08:10:13.000000000 +0200
> @@ -1290,7 +1290,9 @@ static void mxc_setup_config1(void)
> uint16_t tmp;
>
> tmp = readw(&host->regs->nfc_config1);
> +#ifndef MACH_TYPE_TX25
> tmp |= NFC_ONE_CYCLE;
> +#endif
NAK. We cleaned up all u-boot occurrencies of machine id, except the
machid passed to the kernel. And when the device tree will be effective,
also the machid will be obsolete.
This change seems not strictly related to the Karo's SOM, but it it a
configuration of the mxc_nand driver, such as CONFIG_NAND_MXC_V1_1. You
can add a CONFIG_NAND_MXC_* value (please add documentation, too) and
use it in the driver code.
Can I also ask you if the same setup is used in the Linux driver (this
SOM is not mainlined, I suppose you have a porting from the
manufacturer) ? As far as I can see, this setup is not used for the
Freescale's mx25pdk (the only MX25 board in mainline kernel).
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2012-04-01 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 7:31 [U-Boot] [PATCH] Correct corrupted NAND Flash access on KARO TX25 modules Gachet Daniel
2012-03-31 18:31 ` Marek Vasut
2012-04-01 8:56 ` Gachet Daniel
2012-04-01 13:43 ` Marek Vasut
2012-04-01 10:33 ` stefano babic [this message]
2012-04-01 19:09 ` Gachet Daniel
2012-04-01 21:02 ` Marek Vasut
[not found] ` <7605B15734F74B40A124AED46B25250A4F26AD@HEFRMBX01.sofr.hefr.lan>
2012-04-02 13:39 ` Marek Vasut
[not found] ` <7605B15734F74B40A124AED46B25250A4F2809@HEFRMBX01.sofr.hefr.lan>
2012-04-02 18:18 ` stefano babic
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=4F782EE4.7030407@denx.de \
--to=sbabic@denx.de \
--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