From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 05/10 v3] spl, nand: add 4bit HW ecc oob first nand_read_page function
Date: Thu, 27 Oct 2011 13:14:32 -0500 [thread overview]
Message-ID: <4EA99F88.7060500@freescale.com> (raw)
In-Reply-To: <4EA8EAC3.5000804@denx.de>
On 10/27/2011 12:23 AM, Heiko Schocher wrote:
>>> In drivers/mtd/nand/davinci_nand.c CONFIG_SYS_NAND_4BIT_HW_ECC_OOBFIRST
>>> is used, and there are 4bit specific functions, so this define is
>>> also valid, just we need in drivers/mtd/nand/nand_spl_simple.c a more
>>> common name, right?
>>
>> Right. Ideally, though, that would either be CONFIG_SYS_DAVINCI_... or
>> #if defined(CONFIG_SYS_NAND_HW_ECC_OOBFIRST) && \
>> defined(CONFIG_SYS_NAND_HW_ECC_4BIT)
>
> Hmm.. I thought you meant, this is not davinci nor 4bit specific?
> Or do you mean to rename the CONFIG_SYS_NAND_4BIT_HW_ECC_OOBFIRST
> define in drivers/mtd/nand/davinci_nand.c?
I just mean that "4bit" and "oobfirst" are independent things, so I'd
rather not have something that combines the two as part of the
configuration of the general NAND interface in the absence of a
requirement to enumerate all possibilities. OTOH, the structure of
driver's private config can be whatever makes the most sense for that
driver, but should be named in a way that it's obviously driver-specific.
-Scott
next prev parent reply other threads:[~2011-10-27 18:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 14:28 [U-Boot] [PATCH v2 05/10] spl, nand: add 4bit HW ecc oob first nand_read_page function Heiko Schocher
2011-10-05 21:45 ` Scott Wood
2011-10-06 5:41 ` Heiko Schocher
2011-10-06 5:45 ` [U-Boot] [PATCH 05/10 v3] " Heiko Schocher
2011-10-06 16:05 ` Tom Rini
2011-10-10 21:17 ` Scott Wood
2011-10-11 5:41 ` Heiko Schocher
2011-10-11 5:49 ` Wolfgang Denk
2011-10-25 15:24 ` Scott Wood
2011-10-26 6:16 ` Heiko Schocher
2011-10-26 16:58 ` Scott Wood
2011-10-27 5:23 ` Heiko Schocher
2011-10-27 18:14 ` Scott Wood [this message]
2011-10-28 6:05 ` Heiko Schocher
2011-10-28 16:03 ` 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=4EA99F88.7060500@freescale.com \
--to=scottwood@freescale.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