Patch "spi: Check we have a spi_device_id for each DT compatible" has been added to the 5.14-stable tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is a note to let you know that I've just added the patch titled

    spi: Check we have a spi_device_id for each DT compatible

to the 5.14-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     spi-check-we-have-a-spi_device_id-for-each-dt-compat.patch
and it can be found in the queue-5.14 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.



commit 493e4b48ccf9ad46a7db3df58386bf98354ad787
Author: Mark Brown <broonie@xxxxxxxxxx>
Date:   Tue Sep 21 20:21:49 2021 +0100

    spi: Check we have a spi_device_id for each DT compatible
    
    [ Upstream commit 5fa6863ba69265cb7e45567d12614790ff26bd56 ]
    
    Currently for SPI devices we use the spi_device_id for module autoloading
    even on systems using device tree, meaning that listing a compatible string
    in the of_match_table isn't enough to have the module for a SPI driver
    autoloaded.
    
    We attempted to fix this by generating OF based modaliases for devices
    instantiated from DT in 3ce6c9e2617e ("spi: add of_device_uevent_modalias
    support") but this meant we no longer reported spi_device_id based aliases
    which broke drivers such as spi-nor which don't list all the compatible
    strings they support directly for DT, and in at least that case it's not
    super practical to do so given the very large number of compatibles
    needed, much larger than the number spi_device_ids due to vendor strings.
    As a result fell back to using spi_device_id based modalises.
    
    Try to close the gap by printing a warning when a SPI driver has a DT
    compatible that won't be matched as a SPI device ID with the goal of having
    drivers provide both. Given fallback compatibles this check is going to be
    excessive but it should be robust which is probably more important here.
    
    Signed-off-by: Mark Brown <broonie@xxxxxxxxxx>
    Link: https://lore.kernel.org/r/20210921192149.50740-1-broonie@xxxxxxxxxx
    Signed-off-by: Mark Brown <broonie@xxxxxxxxxx>
    Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>

diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
index 3093e0041158c..f6c8565d9300a 100644
--- a/drivers/spi/spi.c
+++ b/drivers/spi/spi.c
@@ -453,6 +453,47 @@ int __spi_register_driver(struct module *owner, struct spi_driver *sdrv)
 {
 	sdrv->driver.owner = owner;
 	sdrv->driver.bus = &spi_bus_type;
+
+	/*
+	 * For Really Good Reasons we use spi: modaliases not of:
+	 * modaliases for DT so module autoloading won't work if we
+	 * don't have a spi_device_id as well as a compatible string.
+	 */
+	if (sdrv->driver.of_match_table) {
+		const struct of_device_id *of_id;
+
+		for (of_id = sdrv->driver.of_match_table; of_id->compatible[0];
+		     of_id++) {
+			const char *of_name;
+
+			/* Strip off any vendor prefix */
+			of_name = strnchr(of_id->compatible,
+					  sizeof(of_id->compatible), ',');
+			if (of_name)
+				of_name++;
+			else
+				of_name = of_id->compatible;
+
+			if (sdrv->id_table) {
+				const struct spi_device_id *spi_id;
+
+				for (spi_id = sdrv->id_table; spi_id->name[0];
+				     spi_id++)
+					if (strcmp(spi_id->name, of_name) == 0)
+						break;
+
+				if (spi_id->name[0])
+					continue;
+			} else {
+				if (strcmp(sdrv->driver.name, of_name) == 0)
+					continue;
+			}
+
+			pr_warn("SPI driver %s has no spi_device_id for %s\n",
+				sdrv->driver.name, of_id->compatible);
+		}
+	}
+
 	return driver_register(&sdrv->driver);
 }
 EXPORT_SYMBOL_GPL(__spi_register_driver);



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux