Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Walle" <mwalle@kernel.org>
To: "Ronan Dalton" <ronan.dalton@alliedtelesis.co.nz>,
	<pratyush@kernel.org>, <takahiro.kuwano@infineon.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
	"Miquel Raynal" <miquel.raynal@bootlin.com>,
	"Richard Weinberger" <richard@nod.at>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Chris Packham" <chris.packham@alliedtelesis.co.nz>,
	"Aryan Srivastava" <aryan.srivastava@alliedtelesis.co.nz>
Subject: Re: [PATCH v2 3/3] mtd: spi-nor: fujitsu: Add support for MB85RS4MTY chip
Date: Wed, 01 Jul 2026 10:05:30 +0200	[thread overview]
Message-ID: <DJN2V8UD53G1.TWK9X1TCEVJ7@kernel.org> (raw)
In-Reply-To: <20260626022108.1963271-6-ronan.dalton@alliedtelesis.co.nz>


[-- Attachment #1.1: Type: text/plain, Size: 1252 bytes --]

Hi,

On Fri Jun 26, 2026 at 4:21 AM CEST, Ronan Dalton wrote:
> The MB85RS4MTY chip is similar to the MB85RS1MT chip, but it has a
> higher capacity and can handle higher temperatures. Compared to the
> MB85RS1MT chip, this chip has an expanded set of opcodes which allow
> control over power-saving modes, access to a special sector data area,
> and reading of the unique ID and serial number. However, since the
> spi-nor subsystem doesn't support these extended abilities, they are not
> taken advantage of here.

I'm sorry, but we don't accept any new parts, which clearly emulates
an EEPROM and has no concept of erase blocks (or don't even emulate
the erase opcode). I understand, that it was very convenient to have
a block device. But I want to move away from that NO_ERASE hack and
having two different drivers for the same hardware device.

Maybe someone in the loop has an idea how to move forward regarding
the filesystem issue.

..

> +	}, {
> +		.id = SNOR_ID(0x04, 0x7f, 0x49),
> +		.name = "mb85rs4mty",

We dropped adding names of the flashes for new parts, because of
notorious id reuse.

-michael

> +		.size = SZ_512K,
> +		.sector_size = SZ_512K,
> +		.flags = SPI_NOR_NO_ERASE
>  	}
>  };
>  

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]

[-- Attachment #2: Type: text/plain, Size: 144 bytes --]

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

  reply	other threads:[~2026-07-01  8:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26  2:21 [PATCH v2 1/3] Revert "mtd: spi-nor: remove Fujitsu MB85RS1MT support" Ronan Dalton
2026-06-26  2:21 ` [PATCH v2 2/3] mtd: spi-nor: fujitsu: Convert to new flash_info format Ronan Dalton
2026-06-26  2:21 ` [PATCH v2 3/3] mtd: spi-nor: fujitsu: Add support for MB85RS4MTY chip Ronan Dalton
2026-07-01  8:05   ` Michael Walle [this message]
2026-07-01 23:48     ` Ronan Dalton
2026-06-30  7:47 ` [PATCH v2 1/3] Revert "mtd: spi-nor: remove Fujitsu MB85RS1MT support" Takahiro.Kuwano
2026-06-30 21:05   ` Chris Packham
2026-07-01  1:10     ` Takahiro.Kuwano
2026-07-01  2:08       ` Ronan Dalton
2026-07-01  8:12         ` Michael Walle
2026-07-01 23:42           ` Ronan Dalton
2026-07-01  9:49         ` Takahiro.Kuwano

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=DJN2V8UD53G1.TWK9X1TCEVJ7@kernel.org \
    --to=mwalle@kernel.org \
    --cc=aryan.srivastava@alliedtelesis.co.nz \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=ronan.dalton@alliedtelesis.co.nz \
    --cc=takahiro.kuwano@infineon.com \
    --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