All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: Sean Anderson <sean.anderson@linux.dev>,
	 Tudor Ambarus <tudor.ambarus@linaro.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:40:48 +0200	[thread overview]
Message-ID: <mafs0wm55mur3.fsf@kernel.org> (raw)
In-Reply-To: <mafs05xcpo9sz.fsf@kernel.org> (Pratyush Yadav's message of "Wed, 08 Oct 2025 14:30:20 +0200")

On Wed, Oct 08 2025, Pratyush Yadav wrote:

> On Tue, Oct 07 2025, Sean Anderson wrote:
>
[...]
>>>> Tested with a mt25qu01gbbb, which shares the same flash ID.
>>> 
>>> Ughh, is this another case of flash ID reuse? Do mt25qu and n25q00a
>>> flashes behave exactly the same and only have two names? If not, then
>>> how do you know if n25q00a will also work with these changes?
>>
>> I examined the datasheet for the n25q00a and determined that it has the
>> same status register layout.
>
> Can you share the links to the datasheets?
>
> Also, test logs would be nice to have.
>
>>
>> In fact, every n25q and mt25q flash has the same status register layout,
>> which (as noted above) is necessary to support capacities greater than 8
>> MiB (and all flashes in this series have such capacity).
>
> Do they behave the same? If not, do you know how they differ? If they

To clarify, I mean behave the same in things other than the status
register.

> behave differently, we might need to have some code that detects which
> one is running. Not necessarily as part of this patch though.
[...]

-- 
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: Pratyush Yadav <pratyush@kernel.org>
Cc: Sean Anderson <sean.anderson@linux.dev>,
	 Tudor Ambarus <tudor.ambarus@linaro.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:40:48 +0200	[thread overview]
Message-ID: <mafs0wm55mur3.fsf@kernel.org> (raw)
In-Reply-To: <mafs05xcpo9sz.fsf@kernel.org> (Pratyush Yadav's message of "Wed, 08 Oct 2025 14:30:20 +0200")

On Wed, Oct 08 2025, Pratyush Yadav wrote:

> On Tue, Oct 07 2025, Sean Anderson wrote:
>
[...]
>>>> Tested with a mt25qu01gbbb, which shares the same flash ID.
>>> 
>>> Ughh, is this another case of flash ID reuse? Do mt25qu and n25q00a
>>> flashes behave exactly the same and only have two names? If not, then
>>> how do you know if n25q00a will also work with these changes?
>>
>> I examined the datasheet for the n25q00a and determined that it has the
>> same status register layout.
>
> Can you share the links to the datasheets?
>
> Also, test logs would be nice to have.
>
>>
>> In fact, every n25q and mt25q flash has the same status register layout,
>> which (as noted above) is necessary to support capacities greater than 8
>> MiB (and all flashes in this series have such capacity).
>
> Do they behave the same? If not, do you know how they differ? If they

To clarify, I mean behave the same in things other than the status
register.

> behave differently, we might need to have some code that detects which
> one is running. Not necessarily as part of this patch though.
[...]

-- 
Regards,
Pratyush Yadav

  reply	other threads:[~2025-10-08 12:40 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
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 [this message]
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=mafs0wm55mur3.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.