On Mon, 2016-06-13 at 17:25 +0300, Mika Westerberg wrote: > On Mon, Jun 13, 2016 at 04:54:31PM +0300, Andy Shevchenko wrote: > > Would work to me, though still the same question: is it possible to > > avoid building it on even most of Intel platforms, since there, I > > assume, will be not many users of the module? > > Well, even if you make it configurable via Kconfig, I guess distros > will > have to enable it in order to support as wide range of CPUs as > possible > in a single binary. Good point. Then perhaps the following we can do: - add a static boolean flag - add __init function where we check either PCI root bridge ID or CPU ID (I don't know which one is better, I suppose second one, though it will require an update of arch/x86/include/asm/intel-family.h) - add a check into the function. What do you think? -- Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> Intel Finland Oy -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html