On Tue, Jan 15, 2019 at 09:17:30AM -0800, Olof Johansson wrote: > I'd argue it's *more* confusing to expect users to know about and > enable some random V4L driver to get this exported kernel API included > or not. Happy to add "If in doubt, say 'n' here" help text, like we do > for many many other kernel config options. It is just like any other library function - you get it with a user. > In this particular case, a module (under early development and not yet > ready to upstream, but will be) worked with a random distro kernel > that enables the kitchen sink of drivers, but not with a more slimmed > down kernel config. Having to enable a driver you'll never use, just > to enable some generic exported helpers, is just backwards. Just develop the damn driver in a kernel tree and let people pull the whole branch like everyone else: problem solved.
