Re: [PATCH] spi: Check we have a spi_device_id for each DT compatible

[Mark Brown <broonie@xxxxxxxxxx>]

On Tue, 21 Sep 2021 20:21:49 +0100, Mark Brown wrote:
> 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.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] spi: Check we have a spi_device_id for each DT compatible
      commit: 5fa6863ba69265cb7e45567d12614790ff26bd56

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