On Tue, May 14, 2019 at 12:03 PM Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > On Mon, May 13, 2019 at 09:48:15PM +0200, Sedat Dilek wrote: > > On Mon, May 13, 2019 at 12:44 PM Andy Shevchenko > > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > > Is it possible to have an info in dmesg log when nxp-nci_i2c kernel > > module is loaded? > > We have 'initcall_debug' for such purposes. > Thanks. That's nice for retrieving helpful informations, especially the proble line (see below). Unload nxp_nci_i2c module... [ 277.362813] NET: Unregistered protocol family 39 ...and reload nxp_nci_i2c module... [ 291.640491] calling nfc_init+0x0/0x8e [nfc] @ 2998 [ 291.640499] nfc: nfc_init: NFC Core ver 0.1 [ 291.640603] NET: Registered protocol family 39 [ 291.640651] initcall nfc_init+0x0/0x8e [nfc] returned 0 after 111 usecs [ 291.653179] calling nxp_nci_i2c_driver_init+0x0/0x1000 [nxp_nci_i2c] @ 2998 [ 291.669584] probe of i2c-NXP1001:00 returned 1 after 16364 usecs [ 291.669841] initcall nxp_nci_i2c_driver_init+0x0/0x1000 [nxp_nci_i2c] returned 0 after 16244 usecs What I mean is (here: btrfs and vboxdrv built as modules)... [ 21.285569] Btrfs loaded, crc32c=crc32c-intel [ 28.823902] vboxdrv: Successfully loaded version 6.0.6_Debian (interface 0x00290008) - Sedat -
