[PATCH v2 3/3] mtd: spi-nor: fujitsu: Add support for MB85RS4MTY chip

[Michael Walle]

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
>  	}
>  };
>  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 297 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20260701/0d9ffb4a/attachment.sig>