public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] spl: nand: simple: replace readb() with chip specific read_buf()
Date: Thu, 16 Jul 2015 16:12:39 +0200	[thread overview]
Message-ID: <20150716161239.0461519b@lilith> (raw)
In-Reply-To: <55A7B62A.8000603@mleia.com>

Hello Vladimir,

On Thu, 16 Jul 2015 16:48:26 +0300, Vladimir Zapolskiy <vz@mleia.com>
wrote:

(cutting short to the essential point remaining)

> > I personally don't think this is the right way; nand_simple.c should be
> > left unchanged and the board should simply not use it since it does not
> > have a simple NAND controller, and instead it should provide its own
> > nand_spl_load_image().
> 
> For me an alternative change to the proposed one is to duplicate
> nand_spl_simple.c functionality in LPC32xx SLC NAND driver. From
> maintenance point of view this is not the best thing to do IMHO.

You're right that some of the functionality present in nand_simple.c is
duplicated elsewhere; however, that functionality is not the one specific
to nand_simple; actually, it is nand_spl_load_image(), the overall load
functionality which should be in no driver at all but of which I see ten
incarnations in ten drivers.

There should be only one nand_spl_load_image(), in its own file, with
placeholders for driver-specific actions such as page read, bad page
check, etc. One day, maybe, there will be a patch for that.

Anyway: you propose changes in the design of the NAND subsystem so that
the SLC controller driver can use the "simple" model, while I think the
SLC controller is not "simple" so it should not be managed as one. This
dilemma is about the NAND subsystem design, which is waaaay outside my
province -- hence my deferring to Scott, who will decide which way this
should go.

> > But hey, I'm not then NAND custodian. Scott: your call. :)
> 
> Anyway thank you for review and comments.

You're welcome!

> --
> With best wishes,
> Vladimir

Amicalement,
-- 
Albert.

  reply	other threads:[~2015-07-16 14:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 23:33 [U-Boot] [PATCH 0/4] lpc32xx: devkit3250 board update Vladimir Zapolskiy
2015-07-15 23:33 ` [U-Boot] [PATCH 1/4] spl: nand: simple: replace readb() with chip specific read_buf() Vladimir Zapolskiy
2015-07-16  8:02   ` Albert ARIBAUD
2015-07-16 11:31     ` Vladimir Zapolskiy
2015-07-16 12:43       ` Albert ARIBAUD
2015-07-16 13:48         ` Vladimir Zapolskiy
2015-07-16 14:12           ` Albert ARIBAUD [this message]
2015-07-16 19:30             ` Scott Wood
2015-07-15 23:33 ` [U-Boot] [PATCH 2/4] nand: lpc32xx: add SLC NAND controller support Vladimir Zapolskiy
2015-07-16 12:53   ` Albert ARIBAUD
2015-07-16 20:14     ` Scott Wood
2015-07-16 20:18       ` Vladimir Zapolskiy
2015-07-16 20:20   ` Scott Wood
2015-07-16 20:29     ` Vladimir Zapolskiy
2015-07-15 23:33 ` [U-Boot] [PATCH 3/4] lpc32xx: devkit3250: update of board configuration Vladimir Zapolskiy
2015-07-16  7:27   ` Albert ARIBAUD
2015-07-16 12:05     ` Vladimir Zapolskiy
2015-07-16 12:45       ` Albert ARIBAUD
2015-07-15 23:33 ` [U-Boot] [PATCH 4/4] lpc32xx: devkit3250: add spl build support Vladimir Zapolskiy

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=20150716161239.0461519b@lilith \
    --to=albert.u.boot@aribaud.net \
    --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