diff options
| author | Javier Martinez Canillas <javier@osg.samsung.com> | 2015-08-20 09:07:14 +0200 |
|---|---|---|
| committer | Jonathan Cameron <jic23@kernel.org> | 2015-08-22 19:07:09 +0100 |
| commit | ed199a11bdfd2957e46984b77a1e1f0927dc9fa0 (patch) | |
| tree | 46a18ccec71ece3b202fd76c11d6d1204ef6a9fe /drivers/iio/frequency | |
| parent | 1c00dcd31d8e71670180ff938f05eb9aef49c84e (diff) | |
| download | blackbird-obmc-linux-ed199a11bdfd2957e46984b77a1e1f0927dc9fa0.tar.gz blackbird-obmc-linux-ed199a11bdfd2957e46984b77a1e1f0927dc9fa0.zip | |
iio: Export SPI module alias information in missing drivers
The SPI core always reports the MODALIAS uevent as "spi:<modalias>"
regardless of the mechanism that was used to register the device
(i.e: OF or board code) and the table that is used later to match
the driver with the device (i.e: SPI id table or OF match table).
So drivers needs to export the SPI id table and this be built into
the module or udev won't have the necessary information to autoload
the needed driver module when the device is added.
Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
Acked-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Diffstat (limited to 'drivers/iio/frequency')
| -rw-r--r-- | drivers/iio/frequency/adf4350.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/iio/frequency/adf4350.c b/drivers/iio/frequency/adf4350.c index 9a6ef3c2edd0..73f27e0a08dd 100644 --- a/drivers/iio/frequency/adf4350.c +++ b/drivers/iio/frequency/adf4350.c @@ -628,6 +628,7 @@ static const struct spi_device_id adf4350_id[] = { {"adf4351", 4351}, {} }; +MODULE_DEVICE_TABLE(spi, adf4350_id); static struct spi_driver adf4350_driver = { .driver = { |
