All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: linux-mtd@lists.infradead.org
Cc: Marek Vasut <marex@denx.de>
Subject: Re: [PATCH 00/10] mtd: spi-nor: cleanups + block protection support updates
Date: Tue, 13 Oct 2015 18:29:14 -0700	[thread overview]
Message-ID: <20151014012914.GE107187@google.com> (raw)
In-Reply-To: <1441137435-52862-1-git-send-email-computersforpeace@gmail.com>

On Tue, Sep 01, 2015 at 12:57:05PM -0700, Brian Norris wrote:
> [Note: as this is sent out during the merge window, it's based on the
> semi-unofficial l2-mtd.git/next branch, which is targeting 4.4, not 4.3]
> 
> Hi all,
> 
> I've been reviewing various spi-nor drivers as well as working with some
> Winbond flash to support new locking features. The former helped point out a
> few more things that could use some improvement, and the latter suggested that
> we have some glaring oversights in the spi-nor lock/unlock code.
> 
> <side note>
> Some helpful companion code, for mtd-utils:
> 
>  http://lists.infradead.org/pipermail/linux-mtd/2015-August/061526.html
> 
> This extends the flash_lock tool so that you can more easily test specific
> ranges, using:
> 
>   # flash_lock --lock /dev/mtdX <offset> <block-count>
>   # flash_lock --unlock /dev/mtdX <offset> <block-count>
>   # flash_lock --islocked /dev/mtdX <offset> <block-count>
> </side note>
> 
> The first half of this series is fairly self-explanatory. The second might take
> a bit of thought, as a formulaic approach is a little more subtle than a
> table-based approach, so I tried to copy the relevant portions distilled from a
> few datasheets and include comments. Please shout if anything deserves more
> explanation or looks funny to you.
> 
> Highlights:
> 
>  * clean up spi-nor.h header
>  * spi-nor now supports MEMISLOCKED
>  * MEM{LOCK,UNLOCK} support is a little more robust and extendible
>  * turn on dual/quad read for Winbond w25q{32,64}dw
>  * enable block protection for Winbond flash
> 
> Regards,
> Brian

Pushed all to l2-mtd.git, with some minor context fixups for patch 8

      parent reply	other threads:[~2015-10-14  1:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 19:57 [PATCH 00/10] mtd: spi-nor: cleanups + block protection support updates Brian Norris
2015-09-01 19:57 ` [PATCH 01/10] mtd: spi-nor: make implicit <linux/bitops.h> dependency explicit Brian Norris
2015-09-01 19:57 ` [PATCH 02/10] mtd: spi-nor: make bitfield constants more consistent Brian Norris
2015-09-01 19:57 ` [PATCH 03/10] mtd: spi-nor: add SPI NOR manufacturer IDs Brian Norris
2015-09-24 20:17   ` Jagan Teki
2015-09-28  0:46     ` Brian Norris
2015-09-28  9:12       ` Jagan Teki
2015-09-28 23:13         ` Brian Norris
2015-10-01  8:12           ` Jagan Teki
2015-10-01 18:43             ` Brian Norris
2015-09-01 19:57 ` [PATCH 04/10] mtd: spi-nor: use SNOR_MFR_* instead of CFI_MFR_* Brian Norris
2015-09-01 19:57 ` [PATCH 05/10] mtd: spi-nor: fixup kernel-doc for flash lock/unlock function pointers Brian Norris
2015-09-01 19:57 ` [PATCH 06/10] mtd: spi-nor: refactor block protection functions Brian Norris
2015-09-01 19:57 ` [PATCH 07/10] mtd: spi-nor: add mtd_is_locked() support Brian Norris
2015-09-02  9:01   ` Marek Vasut
2015-09-02 20:30     ` Brian Norris
2015-09-03  9:43       ` Marek Vasut
2015-09-03 20:29         ` Brian Norris
2015-10-01  9:00   ` Jagan Teki
2015-10-12 16:49     ` Brian Norris
2015-09-01 19:57 ` [PATCH 08/10] mtd: spi-nor: add DUAL_READ for w25q{32,64}dw Brian Norris
2015-09-01 19:57 ` [PATCH 09/10] mtd: spi-nor: support lock/unlock/is_locked for Winbond Brian Norris
2015-09-01 19:57 ` [PATCH 10/10] mtd: spi-nor: disable protection for Winbond flash at startup Brian Norris
2015-10-14  1:29 ` Brian Norris [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=20151014012914.GE107187@google.com \
    --to=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marex@denx.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 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.