All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: Sean Anderson <sean.anderson@linux.dev>,
	 Pratyush Yadav <pratyush@kernel.org>,
	 Michael Walle <mwalle@kernel.org>,
	linux-mtd@lists.infradead.org,
	 Richard Weinberger <richard@nod.at>,
	linux-kernel@vger.kernel.org,
	 Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH] mtd: spi-nor: Enable locking for n25q00a
Date: Wed, 08 Oct 2025 14:38:17 +0200	[thread overview]
Message-ID: <mafs01pndo9fq.fsf@kernel.org> (raw)
In-Reply-To: <27d13306-79a7-40ae-af88-069d1f71f016@linaro.org> (Tudor Ambarus's message of "Wed, 8 Oct 2025 06:05:36 +0100")

On Wed, Oct 08 2025, Tudor Ambarus wrote:

> Hi, Sean,
>
> On 10/6/25 11:38 PM, Sean Anderson wrote:
>> On 10/6/25 18:34, Sean Anderson wrote:
>>> The datasheet for n25q00a shows that the status register has the same
>>> layout as for n25q00, so use the same flags to enable locking support.
>>> These flags should have been added back in commit 150ccc181588 ("mtd:
>
> Were the flags removed upstream and then not added back?
>
>>> spi-nor: Enable locking for n25q128a11"), but they were removed by the
>> 
>> Sorry, this should be commit f80ff13135cb ("mtd: spi-nor: micron-st: Enable locking for n25q00")
>> 
>> https://lore.kernel.org/all/20200421063313.32655-1-js07.lee@samsung.com/
>
> The rule is still true today: I don't queue patches that are not 
> functionally tested, even if they are based on datasheet info.
>
>> 
>>> maintainer...
>
> Don't point fingers please. If you feel the context is worth
> mentioning, specify it in an impersonal way and add a link to the
> discussion in the commit message.

+1.

>
>>>
>>> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
>>> ---
>>> Tested with a mt25qu01gbbb, which shares the same flash ID.
>
> Would you please let us know how you tested the support?
>
> If you feel generous and want to give back to the community, you can also
> describe your testing steps in the documentation from:
> https://docs.kernel.org/driver-api/mtd/spi-nor.html
>
> Also, if there's going to be a v2, please dump the SPI NOR sysfs and
> debugfs data, see how in the link from above. We're keeping a database
> and it will help us differentiate flashes that have the same flash ID
> but different functionalities.

There will need to be a v2. I'm not applying the commit message in its
current form.

Would be nice to have a sysfs and debugfs dump too. Sean, the data we
need can be found in
https://docs.kernel.org/driver-api/mtd/spi-nor.html.

[...]

-- 
Regards,
Pratyush Yadav

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

WARNING: multiple messages have this Message-ID (diff)
From: Pratyush Yadav <pratyush@kernel.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: Sean Anderson <sean.anderson@linux.dev>,
	 Pratyush Yadav <pratyush@kernel.org>,
	 Michael Walle <mwalle@kernel.org>,
	linux-mtd@lists.infradead.org,
	 Richard Weinberger <richard@nod.at>,
	linux-kernel@vger.kernel.org,
	 Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH] mtd: spi-nor: Enable locking for n25q00a
Date: Wed, 08 Oct 2025 14:38:17 +0200	[thread overview]
Message-ID: <mafs01pndo9fq.fsf@kernel.org> (raw)
In-Reply-To: <27d13306-79a7-40ae-af88-069d1f71f016@linaro.org> (Tudor Ambarus's message of "Wed, 8 Oct 2025 06:05:36 +0100")

On Wed, Oct 08 2025, Tudor Ambarus wrote:

> Hi, Sean,
>
> On 10/6/25 11:38 PM, Sean Anderson wrote:
>> On 10/6/25 18:34, Sean Anderson wrote:
>>> The datasheet for n25q00a shows that the status register has the same
>>> layout as for n25q00, so use the same flags to enable locking support.
>>> These flags should have been added back in commit 150ccc181588 ("mtd:
>
> Were the flags removed upstream and then not added back?
>
>>> spi-nor: Enable locking for n25q128a11"), but they were removed by the
>> 
>> Sorry, this should be commit f80ff13135cb ("mtd: spi-nor: micron-st: Enable locking for n25q00")
>> 
>> https://lore.kernel.org/all/20200421063313.32655-1-js07.lee@samsung.com/
>
> The rule is still true today: I don't queue patches that are not 
> functionally tested, even if they are based on datasheet info.
>
>> 
>>> maintainer...
>
> Don't point fingers please. If you feel the context is worth
> mentioning, specify it in an impersonal way and add a link to the
> discussion in the commit message.

+1.

>
>>>
>>> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
>>> ---
>>> Tested with a mt25qu01gbbb, which shares the same flash ID.
>
> Would you please let us know how you tested the support?
>
> If you feel generous and want to give back to the community, you can also
> describe your testing steps in the documentation from:
> https://docs.kernel.org/driver-api/mtd/spi-nor.html
>
> Also, if there's going to be a v2, please dump the SPI NOR sysfs and
> debugfs data, see how in the link from above. We're keeping a database
> and it will help us differentiate flashes that have the same flash ID
> but different functionalities.

There will need to be a v2. I'm not applying the commit message in its
current form.

Would be nice to have a sysfs and debugfs dump too. Sean, the data we
need can be found in
https://docs.kernel.org/driver-api/mtd/spi-nor.html.

[...]

-- 
Regards,
Pratyush Yadav

  reply	other threads:[~2025-10-08 12:38 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 22:34 [PATCH] mtd: spi-nor: Enable locking for n25q00a Sean Anderson
2025-10-06 22:34 ` Sean Anderson
2025-10-06 22:38 ` Sean Anderson
2025-10-06 22:38   ` Sean Anderson
2025-10-08  5:05   ` Tudor Ambarus
2025-10-08  5:05     ` Tudor Ambarus
2025-10-08 12:38     ` Pratyush Yadav [this message]
2025-10-08 12:38       ` Pratyush Yadav
2025-10-07 13:15 ` Pratyush Yadav
2025-10-07 13:15   ` Pratyush Yadav
2025-10-07 14:20   ` Sean Anderson
2025-10-07 14:20     ` Sean Anderson
2025-10-08 12:30     ` Pratyush Yadav
2025-10-08 12:30       ` Pratyush Yadav
2025-10-08 12:40       ` Pratyush Yadav
2025-10-08 12:40         ` Pratyush Yadav
2025-10-09 22:27       ` Sean Anderson
2025-10-09 22:27         ` Sean Anderson
2025-10-09 23:07         ` Pratyush Yadav
2025-10-09 23:07           ` Pratyush Yadav
2025-10-10 15:45           ` Sean Anderson
2025-10-10 15:45             ` Sean Anderson
2025-10-13  7:30             ` Tudor Ambarus
2025-10-13  7:30               ` Tudor Ambarus
2025-10-14 18:25               ` Sean Anderson
2025-10-14 18:25                 ` Sean Anderson
2025-11-10  7:08                 ` Tudor Ambarus
2025-11-10  7:08                   ` Tudor Ambarus
2025-11-10 10:16                   ` Pratyush Yadav
2025-11-10 10:16                     ` Pratyush Yadav
2025-11-10 16:36                   ` Sean Anderson
2025-11-10 16:36                     ` Sean Anderson
2025-11-11  6:07                     ` Tudor Ambarus
2025-11-11  6:07                       ` Tudor Ambarus
2025-11-12 13:10                 ` Miquel Raynal
2025-11-12 13:10                   ` Miquel Raynal
2025-11-12 13:20                   ` Miquel Raynal
2025-11-12 13:20                     ` Miquel Raynal
2025-11-12 13:34                     ` Michael Walle
2025-11-12 13:34                       ` Michael Walle
2025-11-13 15:32                   ` Sean Anderson
2025-11-13 15:32                     ` Sean Anderson
2025-11-14 17:55                     ` Miquel Raynal
2025-11-14 17:55                       ` Miquel Raynal

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=mafs01pndo9fq.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=mwalle@kernel.org \
    --cc=richard@nod.at \
    --cc=sean.anderson@linux.dev \
    --cc=tudor.ambarus@linaro.org \
    --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 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.