Re: [PATCH] drm/ssd130x: Set SPI .id_table to prevent an SPI core warning

Javier Martinez Canillas writes: > Dmitry Baryshkov writes: > >> On Tue, Dec 31, 2024 at 04:34:34PM +0100, Javier Martinez Canillas wrote: >>> Dmitry Baryshkov writes: >>> >>> Hello Dmitry, >>> >>> > On Tue, Dec 31, 2024 at 12:44:58PM +0100, Javier Martinez Canillas wrote: >> >> [...] >> >>>

Re: [PATCH] drm/ssd130x: Set SPI .id_table to prevent an SPI core warning

Dmitry Baryshkov writes: > On Tue, Dec 31, 2024 at 04:34:34PM +0100, Javier Martinez Canillas wrote: >> Dmitry Baryshkov writes: >> >> Hello Dmitry, >> >> > On Tue, Dec 31, 2024 at 12:44:58PM +0100, Javier Martinez Canillas wrote: > > [...] > >> >> Since the check is done even for built-in dri

Re: [PATCH] drm/ssd130x: Set SPI .id_table to prevent an SPI core warning

On Tue, Dec 31, 2024 at 04:34:34PM +0100, Javier Martinez Canillas wrote: > Dmitry Baryshkov writes: > > Hello Dmitry, > > > On Tue, Dec 31, 2024 at 12:44:58PM +0100, Javier Martinez Canillas wrote: [...] > >> Since the check is done even for built-in drivers, drop the condition to > >> only d

Re: [PATCH] drm/ssd130x: Set SPI .id_table to prevent an SPI core warning

Dmitry Baryshkov writes: Hello Dmitry, > On Tue, Dec 31, 2024 at 12:44:58PM +0100, Javier Martinez Canillas wrote: >> The only reason for the ssd130x-spi driver to have an spi_device_id table >> is that the SPI core always reports an "spi:" MODALIAS, even when the SPI >> device has been register

Re: [PATCH] drm/ssd130x: Set SPI .id_table to prevent an SPI core warning

On Tue, Dec 31, 2024 at 12:44:58PM +0100, Javier Martinez Canillas wrote: > The only reason for the ssd130x-spi driver to have an spi_device_id table > is that the SPI core always reports an "spi:" MODALIAS, even when the SPI > device has been registered via a Device Tree Blob. > > Without spi_dev