From: Christoph Fritz <chf.fritz@googlemail.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: linux-mtd@lists.infradead.org,
Marius Achilles <M.Achilles@phytec.de>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH] mtd: cfi_cmdset_0001 - fixup for PC28F512P33TFA
Date: Wed, 02 Apr 2014 01:10:30 +0200 [thread overview]
Message-ID: <1396393830.6474.31.camel@mars> (raw)
In-Reply-To: <OFDA5ED549.208718B9-ONC1257CAD.0068922B-C1257CAD.006990F4@transmode.se>
On Tue, 2014-04-01 at 21:13 +0200, Joakim Tjernlund wrote:
> Christoph Fritz <chf.fritz@googlemail.com> wrote on 2014/04/01 17:09:51:
> > I already tried all sorts of combinations of various delays and 0xff
> > writes, which can be used wasteful without impact. And yes, errors are
> > happening less -- but are still happening (at for example -2°C starting
> > udev or a filesys-bench program like bonnie++).
>
> Amazing Micron still sells these defect chips
Yeah, and it was pain to do all these kinds of tests to get it reliably
working for a real world application where minus degrees can happen. For
me it would be no problem to keep this quirk in my private queue, but
involving a bigger audience seems to be right considering the facts.
> > Sure, it's possible that I missed the holy right
> > delay-0xff-quirk-combination to get this NOR flash reliable working for
> > its specified temperature range. But until nobody has found it, I would
> > prefer to stick to my posted quirk and just disable suspend erase.
>
> Problem is, if you add that quirk no-one will be able to remove it later
> so we
> better make sure there isn't a less intrusive solution.
What about a comment or printk which makes that clear? I anyway don't
think that there are interested users of this specific NOR flash left
using a current kernel -- but who knows, right.
> hmm, have you checked you bus timing? Perhaps you need to relax it
> somewhat.
Sure, I rechecked the WEIM interface (imx35 bus) settings more than
once. I also did testings with most relaxed settings (highest delays
possible). But still, flash errors do occur.
I should mention that a PC28F256P33BFE (a similar 32 MB NOR flash) works
without any quirk in all my testing environments just reliable as it
should be.
> > Maybe someone from Micron can help?
>
> Yes, you should contact them.
Is there anybody out there knowing a contact without the need of going
through a business-ticket-support-hell ?
Thanks
-- Christoph
next prev parent reply other threads:[~2014-04-01 23:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 17:32 [PATCH] mtd: cfi_cmdset_0001 - fixup for PC28F512P33TFA Christoph Fritz
2014-03-31 20:31 ` Joakim Tjernlund
2014-03-31 22:04 ` Christoph Fritz
2014-04-01 8:29 ` Joakim Tjernlund
[not found] ` <OFA7BCC382.7C5EA8B7-ONC1257CAD.002CA0C1-C1257CAD.002EAA92@LocalDomain>
2014-04-01 11:15 ` Joakim Tjernlund
2014-04-01 15:09 ` Christoph Fritz
2014-04-01 19:13 ` Joakim Tjernlund
2014-04-01 23:10 ` Christoph Fritz [this message]
2014-04-02 7:25 ` Joakim Tjernlund
2014-04-02 9:04 ` Christian Riesch
2014-04-04 21:17 ` Christoph Fritz
2014-04-07 8:41 ` Christian Riesch
2014-04-07 9:54 ` Christoph Fritz
[not found] ` <CAAQYJAvRWt7fEyFbYf9UrK4f5TZDu48dyiVwSfm=MXZnzk5E8A@mail.gmail.com>
2014-04-02 9:18 ` Christoph Fritz
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=1396393830.6474.31.camel@mars \
--to=chf.fritz@googlemail.com \
--cc=M.Achilles@phytec.de \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-mtd@lists.infradead.org \
/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