On Fri, 25 Feb 2022, Greg Kroah-Hartman wrote: > On Sat, Feb 12, 2022 at 05:30:59PM +0000, Maciej W. Rozycki wrote: > > Provide information in the kernel log as to what configuration option to > > enable for PCI UART devices that have been blacklisted in the generic > > PCI 8250 UART driver and which have a dedicated driver available to > > handle that has been disabled. The rationale is there is no easy way > > for the user to map a specific PCI vendor:device pair to an individual > > dedicated driver while the generic driver has this information readily > > available and it will likely be confusing that the generic driver does > > not register such a port. > > > > A message is then printed like: > > > > serial 0000:04:00.3: ignoring port, enable SERIAL_8250_PERICOM to handle > > > > when an affected device is encountered and the generic driver rejects it. > > > > Signed-off-by: Maciej W. Rozycki <macro@xxxxxxxxxxx> > > I've applied patch 1 of this series, but this is really an odd one. Thank you. > We don't do this for any other driver subsystem, so why is it really > needed? What is so special about this driver that distros can't > just enable all of the drivers and all is good? What is keeping those > drivers fromb eing enabled? My justification is we have a supposedly generic PCI 8250 UART driver, except it explicitly and silently refuses to handle a handful of devices chosen by their PCI IDs based on that they may have extra features, even though they are otherwise fully compatible with a generic 8250. For distributions it probably does not matter as long as the packager does not forget to enable an option, which itself might be a problem (I've seen distributions missing drivers randomly). A user who configures their kernel on their own may simply not be aware that for one card enabling SERIAL_8250_PCI will do while for another almost identical card they need to use SERIAL_8250_foo instead even though it's just another PCI 8250 UART. Consequently someone may well waste a day trying to figure out why their card does not work (is it faulty perhaps, is there a configuration error with the hardware?). Even if they actually realise it's a kernel config issue, they may still have to go through a trial-and-error experience trying to figure out which driver to enable. While the generic driver knows perfectly well. Then why not make people's life easier and let them know as well what is going on? I don't think we have another case like this, do we? Hence my proposal. Have I made myself clear now? What are your actual arguments against my reasoning? Maciej
