public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <js07.lee@samsung.com>, <michael@walle.cc>, <john.garry@huawei.com>
Cc: linux-mtd@lists.infradead.org, vigneshr@ti.com, js07.lee@gmail.com
Subject: Re: [PATCH v3 2/3] mtd: spi-nor: add 4bit block protection support
Date: Wed, 22 Jan 2020 14:31:28 +0000	[thread overview]
Message-ID: <1780435.Q0f6Nmcn8h@localhost.localdomain> (raw)
In-Reply-To: <0a2c4e9132f7d4f61fd3ce87c5393c65515b937e.camel@samsung.com>

Hi, Jungseung,

On Wednesday, January 22, 2020 1:42:00 PM EET Jungseung Lee wrote:

cut

> > > > +#define SPI_NOR_BP3_SR_BIT6    BIT(18) /*
> > > > +                                        * BP3 is bit 6 of status
> > > > register.
> > > > +                                        * Must be used with
> > > 
> > > Are we safe to replace SPI_NOR_TB_SR_BIT6 and SPI_NOR_BP3_SR_BIT6
> > > with a
> > > SPI_NOR_SR_TB_BIT6_BP3_BIT5? Or maybe with a
> > > SPI_NOR_SR_BP3_BIT6_TB_BIT5, how
> > > is more convenient?
> > 
> > Let's think about some flash in which BP0-3 exists in the status
> > register but TB exists in another register.
> > for example, mx25u12835f.
> > I haven't tested yet, but according to the datasheet, I think this
> > patch can support 4bit block protection for the flash.
> > 
> > In order to embrace the case, how about letting them as It is.
> > Is there any suggestion?

Ok, this info should go in the commit message, together with details about 
which flashes were tested.

I didn't know that the TB bit can be defined in the Configuration register. 
This means that your suggestion with dedicated macros for BP3 and TB is fine.

I looked a bit over your patches, they are in a pretty good shape. I saw 
something that can be improved on patch 2/3, but I didn't manage to finish the 
review. Your patches are the first on my TODO list, but now I'm a bit busy. I 
hope that I'll come with a complete review by the end of the next week. I'm 
going to do tests on few flashes too, to make sure that BP0-2 was not 
affected.

In the meantime, maybe Michael or John can review/test your patches, they 
showed interest in BP0-3 support.

Cheers,
ta


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

  reply	other threads:[~2020-01-22 14:31 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200113055910epcas1p4f97dfeb465b00d66649d6321cffc7b5a@epcas1p4.samsung.com>
2020-01-13  5:59 ` [PATCH v3 1/3] mtd: spi-nor: introduce SR_BP_SHIFT define Jungseung Lee
2020-01-13  5:59   ` [PATCH v3 2/3] mtd: spi-nor: add 4bit block protection support Jungseung Lee
2020-01-14 10:49     ` Tudor.Ambarus
2020-01-17 15:06       ` Jungseung Lee
2020-01-22 11:42         ` Jungseung Lee
2020-01-22 14:31           ` Tudor.Ambarus [this message]
2020-01-22 17:14             ` Michael Walle
2020-01-23  3:59               ` Jungseung Lee
2020-01-23  8:15                 ` Michael Walle
2020-02-11  7:52         ` chenxiang (M)
2020-03-04  5:20           ` Jungseung Lee
2020-03-04  8:36             ` chenxiang (M)
2020-03-07  7:40               ` Jungseung Lee
2020-01-22 19:36     ` Michael Walle
2020-01-23  6:22       ` Jungseung Lee
2020-01-23  8:10         ` Michael Walle
2020-01-23  8:53           ` Jungseung Lee
2020-01-23  9:31             ` Michael Walle
2020-01-28 11:01               ` Jungseung Lee
2020-01-28 12:29                 ` [SPAM] " Michael Walle
2020-01-30  8:17                   ` Jungseung Lee
2020-01-30  8:36                     ` [SPAM] " Michael Walle
2020-01-30 10:07                       ` Jungseung Lee
2020-02-03 13:56                     ` Vignesh Raghavendra
2020-02-03 14:38                       ` [SPAM] " Michael Walle
2020-02-03 14:58                         ` Jungseung Lee
2020-02-03 17:31                         ` Vignesh Raghavendra
2020-02-07 12:17                       ` Tudor.Ambarus
2020-02-10  8:33                         ` Michael Walle
2020-02-10  9:47                           ` Tudor.Ambarus
2020-02-10  9:59                             ` Tudor.Ambarus
2020-02-10 10:40                               ` Michael Walle
2020-02-10 11:27                                 ` Tudor.Ambarus
2020-02-10 12:14                                   ` Michael Walle
2020-02-10 15:50                                     ` Tudor.Ambarus
2020-02-10 10:29                             ` Michael Walle
2020-02-10 11:26                               ` Tudor.Ambarus
2020-02-19 10:50                                 ` Jungseung Lee
2020-02-19 11:08                                   ` Michael Walle
2020-02-19 11:23                                     ` Jungseung Lee
2020-02-19 11:36                                       ` Michael Walle
2020-02-20 19:09                                   ` Michael Walle
2020-02-21  9:30                                     ` Tudor.Ambarus
2020-02-25  8:20                                       ` Tudor.Ambarus
2020-02-25  9:25                                         ` Jungseung Lee
2020-01-13  5:59   ` [PATCH v3 3/3] mtd: spi-nor: support lock/unlock for a few Micron chips Jungseung Lee
2020-01-13 12:30     ` John Garry
2020-01-13 12:40       ` Jungseung Lee
2020-01-13 12:45       ` Jungseung Lee
2020-01-13 13:00         ` John Garry
2020-02-17  0:18   ` [PATCH v3 1/3] mtd: spi-nor: introduce SR_BP_SHIFT define Tudor.Ambarus

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=1780435.Q0f6Nmcn8h@localhost.localdomain \
    --to=tudor.ambarus@microchip.com \
    --cc=john.garry@huawei.com \
    --cc=js07.lee@gmail.com \
    --cc=js07.lee@samsung.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=vigneshr@ti.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