From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nand: fix reading after switching ecc
Date: Tue, 14 Jan 2014 21:56:07 +0100 [thread overview]
Message-ID: <52D5A467.7060209@myspectrum.nl> (raw)
In-Reply-To: <1389732072.24905.109.camel@snotra.buserror.net>
On 01/14/2014 09:41 PM, Scott Wood wrote:
> On Tue, 2014-01-14 at 21:38 +0100, Jeroen Hofstee wrote:
>> On 01/14/2014 09:21 PM, Scott Wood wrote:
>>> All the other cleanup required to change ECC modes is handled by the
>>> OMAP driver; why shouldn't this be as well?
>>
>> If there are more architectures, who think it is brilliant to switch ecc
>> it will become a mesh if not coped with in general. And yes omap might
>> be the exception for now, so lets put it there.
> Perhaps, but solving it in general should not happen via changes like
> this, but rather some sort of reset function that gives you a clean
> slate.
>
I have no problem with a function call to nand_base resetting this
flag, at least nand_base keeps in control of its own flag. I'll send
you a patch for it.
Regards,
Jeroen
next prev parent reply other threads:[~2014-01-14 20:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 13:39 [U-Boot] [PATCH] nand: fix reading after switching ecc Jeroen Hofstee
2014-01-12 9:27 ` Nikita Kiryanov
2014-01-13 8:29 ` Gupta, Pekon
2014-01-13 18:18 ` Scott Wood
2014-01-14 20:11 ` Jeroen Hofstee
2014-01-14 20:21 ` Scott Wood
2014-01-14 20:38 ` Jeroen Hofstee
2014-01-14 20:41 ` Scott Wood
2014-01-14 20:56 ` Jeroen Hofstee [this message]
2014-01-14 21:05 ` Scott Wood
2014-01-14 21:15 ` Jeroen Hofstee
2014-01-14 21:17 ` Scott Wood
2014-01-15 5:56 ` Gupta, Pekon
2014-01-15 16:58 ` [U-Boot] [PATCH v2] nand, gpmc: " Jeroen Hofstee
2014-01-17 13:06 ` [U-Boot] [U-Boot, " Tom Rini
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=52D5A467.7060209@myspectrum.nl \
--to=jeroen@myspectrum.nl \
--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.