From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/8] Switch ARM platforms from integrator-flash to physmap
Date: Wed, 19 Jan 2011 20:48:50 +0000 [thread overview]
Message-ID: <20110119204850.GB6335@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1295462700.5742.76.camel@e102391-lin.cambridge.arm.com>
On Wed, Jan 19, 2011 at 06:45:00PM +0000, Marc Zyngier wrote:
> On Wed, 2011-01-19 at 14:54 +0000, Russell King - ARM Linux wrote:
> > On Fri, Jan 07, 2011 at 02:09:51PM +0000, Marc Zyngier wrote:
> > > As the integrator-flash driver is mostly a duplicate of physmap,
> > > move all users of this driver to physmap and get rid of the
> > > then unused driver.
> >
> > Does MTD guarantee that the vpp will be turned off whenever the physmap
> > module is removed? If not, can it?
>
> Vpp seems to be controlled directly from the chip drivers (using the
> {ENABLE,DISABLE}_VPP macros and a command-set specific state machine),
> and none of the map drivers play with vpp at all, integrator-flash
> included.
>
> By the look of it, it seems pretty safe, though your own experience
> seems to indicate otherwise. It should be quite easy to plug the vpp off
> feature in physmap. I'll give it a go and re-spin the patchset.
No - we need VPP enabled to write to the flash. I'm talking about module
removal. integrator-flash calls back on removal and insertion, where
VPP is controlled at platform level to make sure VPP is turned off.
Also there's the matter of the write enable on Integrator platforms.
That's not the same as VPP - it prevents any write to the flash devices,
even for ID probing. MTD keeps VPP off during such operations.
So, unless physmap is extended with these callbacks, it can't be used
for Integrator. So there's no point converting the other platforms.
prev parent reply other threads:[~2011-01-19 20:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 14:09 [PATCH v2 0/8] Switch ARM platforms from integrator-flash to physmap Marc Zyngier
2011-01-07 14:09 ` [PATCH v2 1/8] MTD: Add integrator-flash feature " Marc Zyngier
2011-01-07 14:09 ` [PATCH v2 2/8] ARM: Realview: Use physmap driver instead of integrator-flash Marc Zyngier
2011-01-07 14:09 ` [PATCH v2 3/8] ARM: Versatile: " Marc Zyngier
2011-01-07 14:09 ` [PATCH v2 4/8] ARM: VExpress: " Marc Zyngier
2011-01-07 14:09 ` [PATCH v2 5/8] ARM: Integrator/AP: " Marc Zyngier
2011-01-07 14:09 ` [PATCH v2 6/8] ARM: Integrator/CP: " Marc Zyngier
2011-01-07 14:09 ` [PATCH v2 7/8] ARM: aaec2000: " Marc Zyngier
2011-01-07 14:09 ` [PATCH v2 8/8] MTD: Remove integrator-flash Marc Zyngier
2011-01-19 14:54 ` [PATCH v2 0/8] Switch ARM platforms from integrator-flash to physmap Russell King - ARM Linux
2011-01-19 18:45 ` Marc Zyngier
2011-01-19 20:48 ` Russell King - ARM Linux [this message]
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=20110119204850.GB6335@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).