> On 26.04.2015, at 13:23, Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > I think there is actual a use for just binding spidev as spidev, > think e.g. the spi pins on the raspberry pi. > > How do you deal we suggest with such a situation ? I actually asked the same question a few days ago on the spi list (in thread: "spi: spidev: Warn loudly if instantiated from DT as “spidev”) and the summary was: You can still do as before, but you have to accept that long irritating warning. Or you patch spidev.c to include your pattern of choice for compatiblity Or you implement the following proposal (which needs a volunteer): > On 23.04.2015, at 09:42, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > > So what you need is a way to handover from generic spidev to a device-specific > driver, cfr. what graphics drivers do when the device has been bound to by > vesafb or simplefb. > > Could this be implemented in a generic way in the spi or DT code? ... > On 23.04.2015, at 12:36, Mark Brown <broonie@xxxxxxxxxx> wrote: > On Thu, Apr 23, 2015 at 09:45:16AM +0200, Geert Uytterhoeven wrote: > >> I guess this has been suggested before: the spi core could provide spidev >> access to all spi client devices which are not bound by a driver? > > I don't know if it's been suggested before, certainly nobody did the > work to make it happen. I don't think I have a massive objection in > principal. Martin -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html