All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Krzeminski, Marcin (Nokia - PL/Wroclaw)" <marcin.krzeminski@nokia.com>
To: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: "rfsw-patches@mlist.nokia.com" <rfsw-patches@mlist.nokia.com>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>,
	"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
	"marek.vasut@gmail.com" <marek.vasut@gmail.com>
Subject: RE: [PATCH 1/3] mtd: spi-nor: Add die_cnt field and flags
Date: Fri, 18 Nov 2016 10:53:19 +0000	[thread overview]
Message-ID: <AM4PR0701MB213010A6B6B0284D8E30427DFEB00@AM4PR0701MB2130.eurprd07.prod.outlook.com> (raw)
In-Reply-To: 0386ac08-f41e-1e10-d0e6-a16624bba952@atmel.com

Cyrille,

....
> >
> > If think you should first check whether nor->erase() is implemented by
> > the SPI controller driver and call it instead of nor->write_reg().
> >
> > For instance, some SPI controllers are mapped to the system memory to
> > speed up Fast Read operations. In which case, they could also enable
> > data cache to fasten even more the read operations.
> >
> > So when the spi-nor framework calls nor->erase() or nor->write(),
> > those handlers might need to invalidate the cache before performing
> > the next read.
> >
> > This is just an example but generally speaking, don't forget the
> > nor->erase() handler! :)
> >
> Thanks for extensive clarification, I will include this in v2.
> 
> Regards,
> Marcin
> 
I've just sent v2 with added check for nor->erase() handler.
As we talked on IRC, with the example you gave above there is
a bug in case of chip erase command, because the driver will not
know that whole flash has been erased.
Maybe there is a need to have a handler in spi-nor framework
for memory invalidation?

Thanks,
Marcin

  parent reply	other threads:[~2016-11-18 10:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 13:03 [PATCH 0/3] Introduce die erase command marcin.krzeminski
2016-10-24 13:03 ` [PATCH 1/3] mtd: spi-nor: Add die_cnt field and flags marcin.krzeminski
2016-10-24 13:54   ` Cyrille Pitchen
2016-10-25  5:43     ` Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-11-18 10:53     ` Krzeminski, Marcin (Nokia - PL/Wroclaw) [this message]
2016-10-24 13:03 ` [PATCH 2/3] mtd: spi-nor: Implement die erase command logic marcin.krzeminski
2016-11-29 16:46   ` Cyrille Pitchen
2016-11-30 16:44     ` Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-11-30 17:20       ` Cyrille Pitchen
2016-11-30 18:18         ` Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-12-09 17:22           ` Cyrille Pitchen
2016-12-16  6:38             ` Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-12-16 10:52               ` Cyrille Pitchen
2016-12-16 13:36                 ` Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-12-19 15:37                   ` Cyrille Pitchen
2016-12-21 16:28                     ` Odp.: " Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-10-24 13:03 ` [PATCH 3/3] mtd: spi-nor: Enable die erase for Micron 1GiB marcin.krzeminski
2016-11-29 16:54   ` Cyrille Pitchen
2016-11-30 17:00     ` Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-11-30 17:32       ` Cyrille Pitchen

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=AM4PR0701MB213010A6B6B0284D8E30427DFEB00@AM4PR0701MB2130.eurprd07.prod.outlook.com \
    --to=marcin.krzeminski@nokia.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@atmel.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=rfsw-patches@mlist.nokia.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 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.