On 11:18 Thu 06 Oct , Uwe Bonnes wrote: > >>>>> "Greg" == Greg KH <gregkh@xxxxxxx> writes: > > Greg> On Wed, Oct 05, 2011 at 11:31:33AM +0200, Uwe Bonnes wrote: > ... > >> Why a special handling for some special device that can be done in > >> user space? > > Greg> How can this be done in userspace? > > Well, userspace can't exactly inhibit the loading of the driver for that > interface, but userspace can unload the driver afterwards. > > >> I would propose to drop ftdi_jtag_probe(), ftdi_8u2232c_probe() and > >> ftdi_stmclite_probe(). > > Greg> Just remove it? Care to provide a patch, with the reasoning why > Greg> this should be applied in the changelog comment and we can review > Greg> it there? > > I would like to get some reasoning of the original patch authors > first. Perhaps there is some stunning reason I don't see yet. For stmclite It's a jtag tools and the uart by default on one port and the other port are manageed by a userspace program so we do not let the uart driver to manage them And some of the hardware are not even configurable UART hard wired to the SOC The FTDI is ofen use on board so you may soon see driver that use the FTDI as a GPIO or SPI bus or I2C bus For Calao board it's more simple the ftdi is on board so hardwired to the uart and the jtag so no need to any configuration at runtime Best Regards, J. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
