[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180802145820.032B11121BE5@debutante.sirena.org.uk>
Date: Thu, 2 Aug 2018 15:58:19 +0100 (BST)
From: Mark Brown <broonie@...nel.org>
To: Frieder Schrempf <frieder.schrempf@...eet.de>
Cc: Boris Brezillon <boris.brezillon@...tlin.com>,
Mark Brown <broonie@...nel.org>, dwmw2@...radead.org,
computersforpeace@...il.com, boris.brezillon@...tlin.com,
marek.vasut@...il.com, richard@....at, broonie@...nel.org,
linux-mtd@...ts.infradead.org, linux-spi@...r.kernel.org,
cyrille.pitchen@...ev4u.fr, frieder.schrempf@...eet.de,
pp@...ix.com, Zhiqiang.Hou@....com, linux-kernel@...r.kernel.org,
linux-spi@...r.kernel.org
Subject: Applied "mtd: m25p80: Call spi_mem_get_name() to let controller set a custom name" to the spi tree
The patch
mtd: m25p80: Call spi_mem_get_name() to let controller set a custom name
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
>From b02b17f55b2e789b9747cf4dd2eaaa110439a4cc Mon Sep 17 00:00:00 2001
From: Frieder Schrempf <frieder.schrempf@...eet.de>
Date: Thu, 2 Aug 2018 14:53:54 +0200
Subject: [PATCH] mtd: m25p80: Call spi_mem_get_name() to let controller set a
custom name
By calling spi_mem_get_name(), the driver of the (Q)SPI controller can
set a custom name for the memory device if necessary.
This is useful to keep mtdparts compatible when controller drivers are
ported from the MTD to the SPI layer.
Suggested-by: Boris Brezillon <boris.brezillon@...tlin.com>
Signed-off-by: Frieder Schrempf <frieder.schrempf@...eet.de>
Acked-by: Boris Brezillon <boris.brezillon@...tlin.com>
Signed-off-by: Mark Brown <broonie@...nel.org>
---
drivers/mtd/devices/m25p80.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/mtd/devices/m25p80.c b/drivers/mtd/devices/m25p80.c
index e84563d2067f..aac488008216 100644
--- a/drivers/mtd/devices/m25p80.c
+++ b/drivers/mtd/devices/m25p80.c
@@ -202,6 +202,9 @@ static int m25p_probe(struct spi_mem *spimem)
if (data && data->name)
nor->mtd.name = data->name;
+ if (!nor->mtd.name)
+ nor->mtd.name = spi_mem_get_name(spimem);
+
/* For some (historical?) reason many platforms provide two different
* names in flash_platform_data: "name" and "type". Quite often name is
* set to "m25p80" and then "type" provides a real chip name.
--
2.18.0
Powered by blists - more mailing lists