linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: "bcousson@baylibre.com" <bcousson@baylibre.com>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v3 2/4] ARM: dts: am437x-gp-evm: add support for parallel NAND flash
Date: Thu, 8 May 2014 13:45:46 -0700	[thread overview]
Message-ID: <20140508204546.GD2198@atomide.com> (raw)
In-Reply-To: <20140507211949.GA19102@atomide.com>

* Tony Lindgren <tony@atomide.com> [140507 14:20]:
> * Gupta, Pekon <pekon@ti.com> [140507 12:20]:
> > >From: Tony Lindgren [mailto:tony@atomide.com]
> > >>* Pekon Gupta <pekon@ti.com> [140422 00:34]:
> > >> +&gpmc {
> > >> +	status = "okay";
> > >> +	pinctrl-names = "default";
> > >> +	pinctrl-0 = <&nand_flash_x8>;
> > >> +	ranges = <0 0 0x08000000 0x10000000>;	/* CS0: NAND */
> > >
> > >Please use the minimum size 16MB GPMC range here, NAND only
> > >has few registers addressable unlike NOR that actually uses the
> > >whole range.
> > >
> > >> +	nand@0,0 {
> > >> +		reg = <0 0 0>; /* CS0, offset 0 */
> > >
> > >Then here map the true size of the NAND device IO register area.
> > >
> > >BTW, we should do the similar changes to other files so we can
> > >unify the GPMC partitioning a bit. But that's unsafe to do until
> > >we have fixed the issue of mapping GPMC devices to a different
> > >location from the bootloader location.
> > >
> > I have found the fix of this issue in gpmc_cs_remap() just testing it
> > using beaglebone NOR cape. I'll post that separately, once I'm confident.
> 
> OK that's great. Yet another issue I've noticed is that u-boot
> seems to program 37xx L3 to run at 200 MHz and the LAN9220
> timings overflow the GPMC registers as 200 / 5 >= 32.

And looks like we have a build warning in the -rc cycle with
omap2plus_defconfig:

drivers/mtd/nand/omap2.c:1250:12: warning: ‘erased_sector_bitflips’ defined but not used [-Wunused-function]

Can you please fix that if not already fixed?

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-05-08 20:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22  7:33 [PATCH v3 0/4] add parallel NAND support for TI's new OMAPx and AMxx platforms (Part-2) Pekon Gupta
2014-04-22  7:33 ` [PATCH v3 1/4] ARM: dts: am335x-bone: add support for beaglebone NAND cape Pekon Gupta
2014-05-06 15:34   ` Tony Lindgren
2014-05-09 18:51     ` Gupta, Pekon
2014-05-12 16:46       ` Tony Lindgren
2014-04-22  7:33 ` [PATCH v3 2/4] ARM: dts: am437x-gp-evm: add support for parallel NAND flash Pekon Gupta
2014-05-06 15:39   ` Tony Lindgren
2014-05-07 19:19     ` Gupta, Pekon
2014-05-07 21:19       ` Tony Lindgren
2014-05-08 20:45         ` Tony Lindgren [this message]
2014-05-09  4:09           ` Gupta, Pekon
2014-05-06 10:41 ` [PATCH v3 0/4] add parallel NAND support for TI's new OMAPx and AMxx platforms (Part-2) Gupta, Pekon

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=20140508204546.GD2198@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=pekon@ti.com \
    /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).