linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Javier Martinez Canillas <martinez.javier@gmail.com>,
	Enric Balletbo Serra <eballetbo@gmail.com>,
	Pekon Gupta <pekon@ti.com>, Tony Lindgren <tony@atomide.com>,
	linux-mtd@lists.infradead.org, Jon Hunter <jgchunter@gmail.com>
Subject: Re: [PATCH 0/3] omap2: Assorted GPMC cleanups
Date: Wed, 6 Nov 2013 16:16:23 -0300	[thread overview]
Message-ID: <20131106191622.GA3162@localhost> (raw)
In-Reply-To: <1382921508-5104-1-git-send-email-ezequiel.garcia@free-electrons.com>

On Sun, Oct 27, 2013 at 09:51:45PM -0300, Ezequiel Garcia wrote:
> (I'm CCing the MTD list, because GPMC is the memory controller
> used for NOR, NAND and OneNAND devices).
> 
> Hi all,
> 
> Just a small patchset containing two small cleanups and a minor fix
> for the GPMC memory controller. The first two are cleanups and can
> be considered as preparation work for the fix.
> 
> The fix is patch 3/3: "Move legacy GPMC width setting". It makes
> explicit use of the DT property "gpmc,device-width" and removes the
> subsequent (and redundant) setting of the GPMC width, based in the
> NAND bus widht.
> 
> Tested in AM335x (using DT) so I'd appreciate if someone can test using
> a board-file, on a device with NAND flash.
> 
> Jon: If you happen to read this, I'd like if you could take a look at
> patch 1/3, since you were the last to touch that part of the code.
> 
> Thanks!
> 
> Ezequiel Garcia (3):
>   omap2: gpmc: Move initialization outside the gpmc_t condition
>   omap2: gpmc: Introduce gpmc_set_legacy()
>   omap2: gpmc: Move legacy GPMC width setting
> 
>  arch/arm/mach-omap2/gpmc-nand.c | 50 +++++++++++++++++++++++------------------
>  1 file changed, 28 insertions(+), 22 deletions(-)
> 

Any comments about this?

Pekon? Maybe you can comment or otherwise ack the patches?

Thanks!
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
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

  parent reply	other threads:[~2013-11-06 19:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28  0:51 [PATCH 0/3] omap2: Assorted GPMC cleanups Ezequiel Garcia
2013-10-28  0:51 ` [PATCH 1/3] omap2: gpmc: Move initialization outside the gpmc_t condition Ezequiel Garcia
2013-10-28  0:51 ` [PATCH 2/3] omap2: gpmc: Introduce gpmc_set_legacy() Ezequiel Garcia
2013-10-28  0:51 ` [PATCH 3/3] omap2: gpmc: Move legacy GPMC width setting Ezequiel Garcia
2013-11-06 19:16 ` Ezequiel Garcia [this message]
2014-01-08 19:18 ` [PATCH 0/3] omap2: Assorted GPMC cleanups Tony Lindgren
2014-01-08 23:38   ` Ezequiel Garcia
2014-01-08 23:40     ` Tony Lindgren

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=20131106191622.GA3162@localhost \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=eballetbo@gmail.com \
    --cc=jgchunter@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=martinez.javier@gmail.com \
    --cc=pekon@ti.com \
    --cc=tony@atomide.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).