From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtdparts: Call nand_init() during mtdparts_init().
Date: Sat, 16 Oct 2010 00:17:01 +0200 [thread overview]
Message-ID: <20101015221701.982F61365CF@gemini.denx.de> (raw)
In-Reply-To: <20101015164801.3fd031b7@udp111988uds.am.freescale.net>
Dear Scott Wood,
In message <20101015164801.3fd031b7@udp111988uds.am.freescale.net> you wrote:
>
> > > it makes more sense to me to hide this in the header (which Scott has done)>
> > > and let the compiler/code optimize dead crap away.
> >
> > Why do we need an explicit call to nand_init() at all?
> >
> > Why cannot the NAND routines check internally if they have been
> > initialized yet, and run nand_init() if and when needed?
>
> mtdparts doesn't make any calls directly to NAND routines (other than
> this new call to nand_init). It looks for registered MTD devices.
>
> Until nand_init runs, you won't have any NAND mtd devices -- and no
> NAND function will be invoked where such initialization could be done.
This looks like a broken design to me.
Assume we add this call here; would it then not also be needed in the
'static' version of mtdparts_init() in "common/cmd_jffs2.c" (whatever
'static' is supposed to mean) ?
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
In the realm of scientific observation, luck is granted only to those
who are prepared. - Louis Pasteur
next prev parent reply other threads:[~2010-10-15 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 18:59 [U-Boot] [PATCH] mtdparts: Call nand_init() during mtdparts_init() Scott Wood
2010-10-15 19:36 ` Wolfgang Denk
2010-10-15 19:47 ` Scott Wood
2010-10-15 20:08 ` Mike Frysinger
2010-10-15 21:39 ` Wolfgang Denk
2010-10-15 21:48 ` Scott Wood
2010-10-15 22:17 ` Wolfgang Denk [this message]
2010-10-15 22:35 ` Scott Wood
2010-10-15 22:48 ` Wolfgang Denk
2010-10-15 23:05 ` 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=20101015221701.982F61365CF@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox