From: Mike Frysinger <vapier.adi@gmail.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Graf Yang <graf.yang@analog.com>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [MTD] [CHIPS] cfi_cmdset_0001.c: put chip into read-array mode after unlocking
Date: Tue, 14 Jul 2009 10:37:07 -0400 [thread overview]
Message-ID: <8bd0f97a0907140737p7b74779vb0f87771e9b460b4@mail.gmail.com> (raw)
In-Reply-To: <20090714143229.GG7572@pengutronix.de>
On Tue, Jul 14, 2009 at 10:32, Wolfram Sang wrote:
>> the CFI layers already go through steps to keep the memory in read
>> mode by default.
>
> Ah, okay. With this assumption, the patch makes sense. Still, the patch
> description should refer more to the above statement and not to watchdogs IMHO.
ok
>> the only way the watchdog could reconfigure the
>> flash is if it were setup to execute software instead of kick the
>> hardware, and that makes the system significantly less reliable.
>
> I meant fixing the watchdog in hardware: If the watchdog pulls the right
> #RESET, the flash will be in read-mode by default. If not, this is an important
> hardware issue.
you're assuming the hardware has this functionality in the first
place. while it is still an issue that should be addressed in
hardware, it's not possible for board designers to do so ;).
-mike
next prev parent reply other threads:[~2009-07-14 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 13:35 [PATCH] [MTD] [CHIPS] cfi_cmdset_0001.c: put chip into read-array mode after unlocking Mike Frysinger
2009-07-14 13:56 ` Wolfram Sang
2009-07-14 14:14 ` Mike Frysinger
2009-07-14 14:32 ` Wolfram Sang
2009-07-14 14:37 ` Mike Frysinger [this message]
2011-04-16 3:13 ` Mike Frysinger
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=8bd0f97a0907140737p7b74779vb0f87771e9b460b4@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=graf.yang@analog.com \
--cc=linux-mtd@lists.infradead.org \
--cc=w.sang@pengutronix.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