From: Vladimir Zapolskiy <vzapolskiy@gmail.com>
To: David Woodhouse <David.Woodhouse@intel.com>
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
linux-mtd@lists.infradead.org,
Mike Frysinger <vapier.adi@gmail.com>,
Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [PATCH] [MTD] physmap: remove physmap_flash_shutdown() method.
Date: Thu, 25 Mar 2010 11:03:26 +0300 [thread overview]
Message-ID: <87iq8krfox.fsf@vovsem.com> (raw)
In-Reply-To: <1268400366-14802-1-git-send-email-vzapolskiy@gmail.com> (Vladimir Zapolskiy's message of "Fri, 12 Mar 2010 16:26:06 +0300")
Hello David,
please could you be so kind to share your objections about the proposed
change?
Thank you in advance.
Vladimir Zapolskiy <vzapolskiy@gmail.com> writes:
> physmap driver operates with cfi, jedec, qinfo and map_rom compliant
> chips. None of interface drivers for all these chips uses actual
> suspend and resume chip operations, but correspondent two methods only
> change flash chip state in drivers' internal state machines, and for
> Intel chips save/restore block locks is done.
>
> To operate with boards with Intel flash chips where RP# pin is not
> asserted on reset there is an already implemented mechanism of reboot
> notifiers, and on reboot the flash moves into defined "read array"
> state.
>
> If CONFIG_PM kernel option is enabled, then physmap_flash_shutdown()
> method is called after reboot notifier work, and save/restore block
> locks operations disturb the chip from default "read array" state,
> thus if the flash is a bootable one, board cann't be booted from it
> after reset.
>
With best wishes,
Vladimir
next prev parent reply other threads:[~2010-03-25 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 13:26 [PATCH] [MTD] physmap: remove physmap_flash_shutdown() method Vladimir Zapolskiy
2010-03-12 13:27 ` Mike Frysinger
2010-03-25 8:03 ` Vladimir Zapolskiy [this message]
2010-04-06 8:58 ` Artem Bityutskiy
2010-04-06 10:11 ` Vladimir Zapolskiy
2010-04-06 10:25 ` Artem Bityutskiy
2010-05-13 23:36 ` David Woodhouse
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=87iq8krfox.fsf@vovsem.com \
--to=vzapolskiy@gmail.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=David.Woodhouse@intel.com \
--cc=buytenh@wantstofly.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.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).