public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nand/denali: Adding Denali NAND driver support
Date: Fri, 12 Sep 2014 00:20:10 -0500	[thread overview]
Message-ID: <1410499210.2021.3.camel@clsee-VirtualBox.altera.com> (raw)
In-Reply-To: <1409710552.24184.90.camel@snotra.buserror.net>

On Tue, 2014-09-02 at 21:15 -0500, Scott Wood wrote:
> On Sat, 2014-08-30 at 07:45 -0400, Tom Rini wrote:
> > On Thu, Aug 28, 2014 at 11:13:40AM +0900, Masahiro Yamada wrote:
> > > Hi Scott,
> > > 
> > > 
> > > On Tue, 19 Aug 2014 04:47:40 -0500
> > > Chin Liang See <clsee@altera.com> wrote:
> > > 
> > > > To add the Denali NAND driver support into U-Boot.
> > > > This driver is leveraged from Linux.
> > > > 
> > > > Signed-off-by: Chin Liang See <clsee@altera.com>
> > > > Cc: Scott Wood <scottwood@freescale.com>
> > > > Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
> > > > ---
> > > > Changes for v9
> > > > - Updated the commit messageb
> > > > - Removed macro kern_xx
> > > > - Removed debug macro
> > > > - Changed CONFIG_NAND_DENALI_64BIT to CONFIG_SYS_NAND_DENALI_64BIT
> > > 
> > > 
> > > Any comments?
> > > 
> > > If nothing, please apply this patch.
> > 
> > I don't see anything obviously wrong here, but since Scott has reviewed
> > previous versions I want to give him a little more time to ack.  I'm OK
> > pulling this into master with Scott's ack or lets say Wednesday next
> > week and we'll ask Chin Liang to address any late feedback.  Thanks all!
> 
> I still don't see a reference to the SHA of the corresponding Linux
> driver.
> 

I will add it in commit message. Its
fdbad98dff8007f2b8bee6698b5d25ebba0471c9


> #define MODE5_WORKAROUND 0 still exists even though it's never used.
> 

Sorry as forget to update the header file. Done


> I still see (void *) casts in memcpy -- v8 comments said "removed" but
> not all instances were removed.
> 

Done


> It still introduces CONFIG_SYS_NAND_DENALI_64BIT without documenting it.

I already added into comments of the code. Let me add it into  commit
message.

Thanks
Chin Liang

> 
> -scott
> 
> 

  parent reply	other threads:[~2014-09-12  5:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19  9:47 [U-Boot] [PATCH] nand/denali: Adding Denali NAND driver support Chin Liang See
2014-08-20  3:47 ` Masahiro Yamada
2014-08-28  2:13 ` Masahiro Yamada
2014-08-30 11:45   ` Tom Rini
2014-09-01  3:54     ` Masahiro Yamada
2014-09-03  2:07       ` Scott Wood
2014-09-03  2:15     ` Scott Wood
2014-09-05  3:01       ` Masahiro Yamada
2014-09-08  9:36         ` Chin Liang See
2014-09-12  5:20       ` Chin Liang See [this message]
     [not found] <D32F37106BA492429BA67AF5061FA1A266515302@NACLMBX01.optos.eye>
2014-06-02  5:14 ` Chin Liang See
  -- strict thread matches above, loose matches on Subject: below --
2013-12-18 21:18 Chin Liang See
2014-01-09 14:47 ` Chin Liang See
2014-02-04 19:07 ` Chin Liang See
2014-02-21 10:57   ` Masahiro Yamada
2014-02-21 20:49     ` Chin Liang See

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=1410499210.2021.3.camel@clsee-VirtualBox.altera.com \
    --to=clsee@altera.com \
    --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