From: Roger Quadros <rogerq@ti.com>
To: Tony Lindgren <tony@atomide.com>, pekon@pek-sem.com
Cc: computersforpeace@gmail.com, dwmw2@infradead.org,
ezequiel@vanguardiasur.com.ar, linux-mtd@lists.infradead.org,
linux-omap@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: omap: Fix NAND enumeration on 3430 LDP
Date: Fri, 7 Nov 2014 11:58:03 +0200 [thread overview]
Message-ID: <545C97AB.4040402@ti.com> (raw)
In-Reply-To: <545C9267.7060301@ti.com>
On 11/07/2014 11:35 AM, Roger Quadros wrote:
> On 11/06/2014 08:03 PM, Tony Lindgren wrote:
>> * Roger Quadros <rogerq@ti.com> [141105 03:02]:
>>> In commit 7d5929c1f343 ("mtd: nand: omap: Revert to using software ECC by default"),
>>> we switched back to using 1-bit SW ECC scheme by default. However
>>> commit b491da7233d5 ("mtd: nand: omap: clean-up ecc layout for BCH ecc schemes")
>>> didn't take into account the 1-bit SW scheme (i.e. OMAP_ECC_HAM1_CODE_SW)
>>> when checking for small page devices because it was already got rid of
>>> one commit earlier. Consider OMAP_ECC_HAM1_CODE_SW while deciding
>>> if we can proceed with small page devices or not.
>>>
>>> Fixes: 7d5929c1f34 ("mtd: nand: omap: Revert to using software ECC by default")
>>>
>>> Cc: <stable@vger.kernel.org> [3.17+]
>>> Reported-by: Tony Lindgren <tony@atomide.com>
>>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>>> ---
>>> drivers/mtd/nand/omap2.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
>>> index 3b357e9..758e594 100644
>>> --- a/drivers/mtd/nand/omap2.c
>>> +++ b/drivers/mtd/nand/omap2.c
>>> @@ -1742,7 +1742,8 @@ static int omap_nand_probe(struct platform_device *pdev)
>>> }
>>>
>>> /* check for small page devices */
>>> - if ((mtd->oobsize < 64) && (pdata->ecc_opt != OMAP_ECC_HAM1_CODE_HW)) {
>>> + if ((mtd->oobsize < 64) && (pdata->ecc_opt != OMAP_ECC_HAM1_CODE_HW) &&
>>> + (pdata->ecc_opt != OMAP_ECC_HAM1_CODE_SW)) {
>>> dev_err(&info->pdev->dev, "small page devices are not supported\n");
>>> err = -EINVAL;
>>> goto return_error;
>>
>> Should this maybe have || instead of && For the OMAP_ECC_HAM1_CODE_SW?
>
> The code is right.
>
> there is a bug in omap3-ldp.dts.
>
> there it says
> ti,nand-ecc-opt = "bch8";
>
> This is wrong. OMAP3 doesn't support bch8. I think you should use either "ham1" or "sw"
Well I'm wrong about the OMAP3 information. OMAP3 does support BCH4 and BCH8 as well.
I'm don't thinkg small page check is right. For BCH8 we need 13 bytes per 512 bytes.
In the LDP case we have page size:1024 and OOB size: 32.
Thus for BCH8 we need 26 bytes per page. which should fit in 32 bytes OOB.
So this check is bogus in that case.
Pekon,
can you please explain why you check for 64 bytes OOB size for all ECC schemes?
Tony,
The question for backward compatibility still remains. Even if OMAP3 supports bch8
do we stick to the scheme that was used in legacy boot or do we switch?
Then there is the question of boot rom compatibility. OMAP3 bootloaders use HAM1 scheme.
So if you want to be able to flash bootloader from the kernel we have to stick with HAM1.
changing the ECC scheme would mean that NAND filesystems created earlier won't work
and will have to be erased and recreated.
cheers,
-roger
next prev parent reply other threads:[~2014-11-07 9:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 11:00 [PATCH] mtd: nand: omap: Fix NAND enumeration on 3430 LDP Roger Quadros
2014-11-06 18:03 ` Tony Lindgren
2014-11-07 9:35 ` Roger Quadros
2014-11-07 9:58 ` Roger Quadros [this message]
2014-11-07 22:48 ` Tony Lindgren
2014-11-09 19:29 ` pekon
2014-11-12 18:02 ` Tony Lindgren
2014-11-13 11:29 ` Roger Quadros
2014-11-13 16:00 ` Tom Rini
2014-11-13 17:54 ` Tony Lindgren
2014-11-15 11:12 ` pekon
2014-11-13 12:00 ` Roger Quadros
2014-11-19 12:22 ` [PATCH v2] " Roger Quadros
2014-11-26 6:47 ` Brian Norris
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=545C97AB.4040402@ti.com \
--to=rogerq@ti.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=pekon@pek-sem.com \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).