On Mon, Jul 06, 2015 at 09:49:51AM -0700, Linus Torvalds wrote: > On Mon, Jul 6, 2015 at 9:07 AM, Samuel Ortiz <sameo@xxxxxxxxxxxxxxx> wrote: > > > > I suppose you were not seeing this issue on e.g. a 4.1 kernel (assuming > > this is not a brand new laptop) ? > > Nope, 4.1 is fine. This is my travel laptop for the last almost two > years. Best laptop I've ever had (I like them small and light). > > > If that's the case, is any of the pn544* kernel modules loaded when > > running on top of a good kernel ? > > So it doesn't show up in lsmod, but presumably the module got loaded > and then errored out or something. The mei and mei_me modules are > loaded, nut no pn544_mei. Oh, by 'good kernel' I meant a 4.1 one for example, sorry for the confusion. Not one where you removed the UUID from pn544/mei.c because thay will essentially make sure the driver is never probed. What I'm trying to rule out is that you never saw that issue on previous kernels because the pn544 driver was not loaded at all, but this: > I'm not even sure why it's in my configuration, because I tend to try > to keep those small, and my config was generated (long ago) with "make > localmodconfig", but maybe there's something non-obvious that brought > it in. Presumably that pn544 module was loaded at _some_ point in the > past. seems to prove it has already been automatically loaded (and thus probed because the loading happened as the NFC device was found on the MEI bus). The pn544 mei support was added with 3.10 iirc, so starting from there your pn544* modules have been most likely automatically loaded. Cheers, Samuel. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
