Received-SPF: pass (google.com: domain of linux-kernel+bounces-204273-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Content-Type: multipart/signed;
 boundary=1cc637e5afad55ee26a7009fa07180f3ee198532ca034bcf93ed2a891362;
 micalg=pgp-sha384; protocol="application/pgp-signature"
Date: Thu, 06 Jun 2024 14:33:39 +0200
Message-Id: <D1SXR8ZVNR3F.2SNEOVX5ZC6G5@kernel.org>
Cc: "Pratyush Yadav" <pratyush@kernel.org>, "Miquel Raynal"
 <miquel.raynal@bootlin.com>, "Richard Weinberger" <richard@nod.at>,
 "Vignesh Raghavendra" <vigneshr@ti.com>, "Rob Herring" <robh@kernel.org>,
 "Krzysztof Kozlowski" <krzk+dt@kernel.org>, "Conor Dooley"
 <conor+dt@kernel.org>, <linux-mtd@lists.infradead.org>,
 <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
 =?utf-8?q?Uwe_Kleine-K=C3=B6nig?= <u.kleine-koenig@pengutronix.de>, "Marek
 Vasut" <marex@denx.de>, "Imre Kaloz" <kaloz@openwrt.org>, "Andrew Lunn"
 <andrew@lunn.ch>, "Flavio Suligoi" <f.suligoi@asem.it>,
 <kernel@pengutronix.de>
From: "Michael Walle" <mwalle@kernel.org>
To: "Tudor Ambarus" <tudor.ambarus@linaro.org>, "Thorsten Scherer"
 <T.Scherer@eckelmann.de>
Subject: Re: [PATCH] dt-bindings: mtd: spi-nor: deprecate Everspin MRAM
 devices
References: <20240604074231.1874972-1-mwalle@kernel.org>
 <kl4ikwh4fpkhhlpneuujyk2j4a2byif7l27n7kgb4pm72hb4an@akhbc4jg6hyq>
 <1094fbfd-0ee7-430e-b62c-20764c1fbeec@linaro.org>
In-Reply-To: <1094fbfd-0ee7-430e-b62c-20764c1fbeec@linaro.org>
Precedence: bulk

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

Hi,

On Thu Jun 6, 2024 at 2:14 PM CEST, Tudor Ambarus wrote:
> > The ci4x10 is still being used and sold.  Right now I do not have a cle=
ar
> > view on the implications of moving to that driver.  I'd like to invest =
some
> > time to sharpen my picture (or find the person that claims responsibili=
ty), but
> > this will propably not happen this week.
> >=20
>
> if it's used then we are forced to keep the entry in SPI NOR for
> backward compatibility. But we can still deprecate the use and forbid
> new support in SPI NOR while directing users to the other driver.

As mentioned, this is intended to be the first step towards removal.
And yes, we won't accept any new such devices, but at the same time,
new device trees should refrain from using this compatible, thus the
mark as deprecated.

How to handle boards which are actively using this device is a
different topic. I'm sure there is some kind of deprecation process.
I doubt we are forced to keep that support until the end of the
world :) Maybe some kind of grace period where we nag the user to
switch to a different interface, etc. Not sure.

Any ideas are welcome.

-michael

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

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

iKgEABMJADAWIQTIVZIcOo5wfU/AngkSJzzuPgIf+AUCZmGsoxIcbXdhbGxlQGtl
cm5lbC5vcmcACgkQEic87j4CH/gn2AF8CcOTEM8x6BLUFvKR6+ekuxoYS/63p47G
6ph5zNQVYwJNufYOwBjvmv17D1kMUY12AYDDc/RYlTNDrJhQra9djygf5N8N0F5T
5mt2/Xrf/vrCDSAPxdcdb2vsF/O7tY28EA4=
=741n
-----END PGP SIGNATURE-----

--1cc637e5afad55ee26a7009fa07180f3ee198532ca034bcf93ed2a891362--