Received-SPF: pass (google.com: domain of linux-kernel+bounces-148746-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Content-Type: multipart/signed;
 boundary=c423f377f76eebb1c0e9a87ea3b3550e31e5e58260f6d25ee91339b00ae2;
 micalg=pgp-sha384; protocol="application/pgp-signature"
Date: Wed, 17 Apr 2024 17:02:57 +0200
Message-Id: <D0MHMBLVCCZ2.23XGMIORQYGDR@kernel.org>
Subject: Re: [PATCH v1 0/6] mtd: spi-nor: spring cleaning
Cc: <linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>
From: "Michael Walle" <mwalle@kernel.org>
To: "Tudor Ambarus" <tudor.ambarus@linaro.org>, "Pratyush Yadav"
 <pratyush@kernel.org>, "Miquel Raynal" <miquel.raynal@bootlin.com>,
 "Richard Weinberger" <richard@nod.at>, "Vignesh Raghavendra"
 <vigneshr@ti.com>
References: <20240412134405.381832-1-mwalle@kernel.org>
 <f07afa83-1c37-49da-923f-2ea9550e7163@linaro.org>
In-Reply-To: <f07afa83-1c37-49da-923f-2ea9550e7163@linaro.org>
Precedence: bulk

--c423f377f76eebb1c0e9a87ea3b3550e31e5e58260f6d25ee91339b00ae2
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8

Hi,

On Tue Apr 16, 2024 at 6:57 AM CEST, Tudor Ambarus wrote:
> On 4/12/24 14:43, Michael Walle wrote:
> > It's time for some spring cleaning. Remove the oddball xilinx
> > flashes with non-power-of-2 page sizes.
> > Remove the .setup() callback, only the default callback is ever
> > used and it is unlikely there is need for a custom setup.
> >=20
> > Finally, the last patch is a proposal how to deprecate flashes,
> > which are just detected by their id. We cannot really find out if
> > there are boards out there which are using a particular flash. Thus,
> > as a first step, we can print a warning during kernel startup. As a
> > second step we might introduce a kernel config option to actually
> > disable the flashes which has the deprecated flag.
>
>
> How many FRAMs/MRAMs are in SPI NOR? Can you list them please? I don't
> remember anyone bringing topics about everspin and the cypress thingy
> was a mistake. I'd like to get an idea whether it's fine to remove the
> FRAM/MRAM from SPI NOR without doing these preparation steps and waiting
> for another year.

As far as I can tell it is just
  drivers/mtd/spi-nor/evervision.c:
   - mr25h128
   - mr25h256
   - mr25h10
   - mr25h40
and
  drivers/mtd/spi-nor/spansion.c
   - cy15x104q

Please keep in mind that the evervision also have dt bindings and
spi aliases. So we'd also have to deprecate these ones. Not sure
they can easily be moved over to another driver, esp. because the
kernel interface is different (mtd partitions vs nvmem/eeprom sysfs
file).

There are three in-tree kernel boards using the mr25h frams:
arch/arm/boot/dts/nxp/imx/imx6dl-eckelmann-ci4x10.dts
No clue about that one.

arch/arm/boot/dts/nxp/mxs/imx28-sps1.dts
I've contacted Marek who introduced support for this board and he
said it can likely be removed altogether.

arch/arm/boot/dts/marvell/armada-xp-linksys-mamba.dts
This seem to be openwrt driven (?)

I was thinking about sending patches to migrate them over to the
at25 driver. But again, that also means they'll loose mtd
partitions. Not sure, that fram is used on these boards anyway.

In any case I'd like to start with deprecating the FRAMs in
spi-nor and the DT bindings.

Also, the cy15x104g is rather new...

-michael

--c423f377f76eebb1c0e9a87ea3b3550e31e5e58260f6d25ee91339b00ae2
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iKgEABMJADAWIQTIVZIcOo5wfU/AngkSJzzuPgIf+AUCZh/koRIcbXdhbGxlQGtl
cm5lbC5vcmcACgkQEic87j4CH/hppgF/eysfe0XwOiW1dI8MpG8NU6Y7AGPTH1od
7JCUF8xW6WoUkGyZNfy9WwDoa1PhjO5rAYDyPS9TGbQ2HIvGO8GclixI+fqq9b04
UT2uLi0rfeoBXHUDGibDVLs5k7qonhxjeIc=
=3qxk
-----END PGP SIGNATURE-----

--c423f377f76eebb1c0e9a87ea3b3550e31e5e58260f6d25ee91339b00ae2--