[U-Boot] [PATCH 1/3] ARM: omap: Fix GPMC init for OMAP3 platforms

Tom Rini trini at ti.com
Fri Jul 11 20:52:20 CEST 2014


On Thu, Jul 10, 2014 at 07:28:00AM +0200, Stefan Roese wrote:
> Hi Pekon,
> 
> On 09.07.2014 20:22, Gupta, Pekon wrote:
> >>Commit a0a37183 (ARM: omap: merge GPMC initialization code for all
> >>platform) broke NAND on OMAP3 based platforms. I noticed this while
> >>testing the latest 2014.07-rc version on the TAO3530 board. NAND
> >>detection did not work with this error message:
> >>
> >>NAND:  nand: error: Unable to find NAND settings in GPMC Configuration - quitting
> >>
> >>As OMAP3 configs don't set CONFIG_NAND but CONFIG_NAND_CMD. the GPMC
> >>was not initialized for NAND at all. This patch now fixes this issue.
> >>
> >Sorry couldn't understand this, why have users enabled CONFIG_NAND_CMD,
> >if CONFIG_NAND itself is not enabled ?
> 
> CONFIG_NAND doesn't seem to be a mandatory define if NAND is used.

Exactly.  Adding in CONFIG_NAND is something that am335x started doing
because of the cases where we do, or do not, want to assume NAND exists.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140711/b2e8f25b/attachment.pgp>


More information about the U-Boot mailing list