From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 1/2 v2] nand: allow delayed initialization
Date: Sun, 03 Oct 2010 23:40:32 +0200 [thread overview]
Message-ID: <20101003214032.E901A1539A0@gemini.denx.de> (raw)
In-Reply-To: <201010031632.47732.vapier@gentoo.org>
Dear Mike Frysinger,
In message <201010031632.47732.vapier@gentoo.org> you wrote:
>
> > Would it not be esier to rename your nand_delayed_init() into
> > nand_init(), and add a "#ifndef CONFIG_SYS_NAND_DELAYED_INIT" around
> > the current call to nand_init()?
>
> nand_init() cant handle being called multiple times. and i need to add more
> nand_init() points that only apply to when things are delayed. so when
> delayed init is not enabled (the default), there is no change in compiled code
> size.
Well, you have this in your new nand_init() code:
+ static uint8_t initialized;
+ if (initialized)
+ return;
+ initialized = 1;
Why cannot we call nand_init() multiple times, then?
> > Question: is there a risk of problems with boards that have the
> > environment in NAND?
>
> that's why my patch adds delayed init points to the major nand env entry
> points. my understanding is that these must be called before the env
> read/write funcs may be called.
OK, just wanted to make sure.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Everybody is talking about the weather but nobody does anything
about it." - Mark Twain
next prev parent reply other threads:[~2010-10-03 21:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 23:45 [U-Boot] [RFC PATCH 1/2] nand: allow delayed initialization Mike Frysinger
2010-09-21 23:45 ` [U-Boot] [PATCH 2/2] Blackfin: nand: support " Mike Frysinger
2010-10-02 19:47 ` [U-Boot] [RFC PATCH 1/2 v2] nand: allow " Mike Frysinger
2010-10-03 18:27 ` Wolfgang Denk
2010-10-03 20:32 ` Mike Frysinger
2010-10-03 21:40 ` Wolfgang Denk [this message]
2010-10-03 22:19 ` Mike Frysinger
2010-10-06 20:40 ` Wolfgang Denk
2010-10-07 17:00 ` Mike Frysinger
2010-10-07 19:35 ` Wolfgang Denk
2010-10-07 21:26 ` Mike Frysinger
2010-10-08 2:00 ` Mike Frysinger
2010-10-10 8:37 ` Mike Frysinger
2010-10-10 9:20 ` Wolfgang Denk
2010-10-04 17:36 ` Scott Wood
2010-10-05 8:08 ` Mike Frysinger
2010-10-05 16:31 ` Scott Wood
2010-10-05 18:27 ` Wolfgang Denk
2010-10-05 19:18 ` Scott Wood
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=20101003214032.E901A1539A0@gemini.denx.de \
--to=wd@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.