linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: David Clear <dac2@pensando.io>
To: Tudor.Ambarus@microchip.com
Cc: michael@walle.cc, linux-mtd@lists.infradead.org
Subject: Re: [BUG]: spi-nor: spi_nor_init() fails when SR locked
Date: Tue, 21 Jul 2020 10:02:02 -0700	[thread overview]
Message-ID: <CA+nMikFjaWtzHnxALYvyHfqkpXnHA-i3K86hPEwFQ+-gOm2O0g@mail.gmail.com> (raw)
In-Reply-To: <1ae4f44a-cbd2-b39e-68f7-3d0375c453bf@microchip.com>

On Tue, Jul 21, 2020 at 2:37 AM <Tudor.Ambarus@microchip.com> wrote:
> We tackled the unlock_all stuff in
> the past, Michael did a patch, I'll check how that fits here.

Thanks Tudor.  The new Macronix mx662ug45g flash in my patch also
supports similar block protections, with WP#, but it looks like the driver
doesn't support BP in any of the Macronix flashes.

The functionality is similar to Micron's (power-of-2 sectors, top/bottom,
WP# lock), with two differences:
1. The BP bits in the SR are in different positions
2. The Top/Bottom bit is OTP, and is in the Configuration Register

As Macronix flashes don't declare BP support it looks like they won't suffer
this specific issue (I'll verify in the next few days), but I'd like to
evolve the driver to support BP on these devices.

Thanks for the patch pointer.  I'll take a look at it.

Regards,
David.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2020-07-21 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 18:13 [BUG]: spi-nor: spi_nor_init() fails when SR locked David Clear
2020-07-21  9:37 ` Tudor.Ambarus
2020-07-21 17:02   ` David Clear [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=CA+nMikFjaWtzHnxALYvyHfqkpXnHA-i3K86hPEwFQ+-gOm2O0g@mail.gmail.com \
    --to=dac2@pensando.io \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    /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).