[v1,0/3] mtd: Ensure DT compatibles have SPI device IDs

Message ID	20210923194827.53229-1-broonie@kernel.org
Headers	show Delivered-To: patch@linaro.org Received-SPF: pass (google.com: best guess record for domain of linux-mtd-bounces+patch=linaro.org@lists.infradead.org designates 2607:7c80:54:e::133 as permitted sender) client-ip=2607:7c80:54:e::133; From: Mark Brown <broonie@kernel.org> To: Miquel Raynal <miquel.raynal@bootlin.com>, Richard Weinberger <richard@nod.at>, Vignesh Raghavendra <vigneshr@ti.com> Cc: linux-mtd@lists.infradead.org, Mark Brown <broonie@kernel.org> Subject: [PATCH v1 0/3] mtd: Ensure DT compatibles have SPI device IDs Date: Thu, 23 Sep 2021 20:48:24 +0100 Message-Id: <20210923194827.53229-1-broonie@kernel.org> MIME-Version: 1.0 preview: Currently autoloading for SPI devices does not use the DT ID table, it uses SPI modalises. Supporting OF modalises is going to be difficult if not impractical, an attempt was made but has been reverte [...] Content analysis details: (-5.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at https://www.dnswl.org/, high trust [198.145.29.99 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.2 DKIMWL_WL_HIGH DKIMwl.org - High trust sender Precedence: list Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-mtd" <linux-mtd-bounces@lists.infradead.org> Errors-To: linux-mtd-bounces+patch=linaro.org@lists.infradead.org
Series	mtd: Ensure DT compatibles have SPI device IDs \| expand [v1,0/3] mtd: Ensure DT compatibles have SPI device IDs [v1,1/3] mtd: dataflash: Add SPI ID table [v1,2/3] mtd: mchp23k256: Add SPI ID table [v1,3/3] mtd: mchp48l640: Add SPI ID table

Message ID

20210923194827.53229-1-broonie@kernel.org

Headers

Received-SPF: pass (google.com: best guess record for domain of
	linux-mtd-bounces+patch=linaro.org@lists.infradead.org
	designates 2607:7c80:54:e::133 as permitted sender)
	client-ip=2607:7c80:54:e::133; 
From: Mark Brown <broonie@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>
Cc: linux-mtd@lists.infradead.org,
	Mark Brown <broonie@kernel.org>
Subject: [PATCH v1 0/3] mtd: Ensure DT compatibles have SPI device IDs
Date: Thu, 23 Sep 2021 20:48:24 +0100
Message-Id: <20210923194827.53229-1-broonie@kernel.org>
MIME-Version: 1.0
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "linux-mtd" <linux-mtd-bounces@lists.infradead.org>
Errors-To: linux-mtd-bounces+patch=linaro.org@lists.infradead.org

Series

mtd: Ensure DT compatibles have SPI device IDs | expand

Message

Mark Brown Sept. 23, 2021, 7:48 p.m. UTC

Currently autoloading for SPI devices does not use the DT ID table, it uses
SPI modalises. Supporting OF modalises is going to be difficult if not
impractical, an attempt was made but has been reverted, so this series
adds SPI IDs where they aren't provided for a given modalias.

Mark Brown (3):
  mtd: dataflash: Add SPI ID table
  mtd: mchp23k256: Add SPI ID table
  mtd: mchp48l640: Add SPI ID table

 drivers/mtd/devices/mchp23k256.c    | 14 ++++++++++++++
 drivers/mtd/devices/mchp48l640.c    | 10 ++++++++++
 drivers/mtd/devices/mtd_dataflash.c |  8 ++++++++
 3 files changed, 32 insertions(+)


base-commit: e73f0f0ee7541171d89f2e2491130c7771ba58d3
-- 
2.20.1


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