The Kernel knows. But how ? Did the acpi make a secret dead drop ?

[Jay Aurabind]

On Sun, 6 Jan 2019 at 16:49, Valentin Vidic <Valentin.Vidic at carnet.hr>
wrote:

> On Sun, Jan 06, 2019 at 02:22:34PM +0530, Jay Aurabind wrote:
> > The subject line might be a bit dramatic, but I assure you my question is
> > isn't.
> >
> > I have a 3-axis accelerometer (LIS3LV02DL) in my laptop which shows up as
> > an input device. Since its x86, I am assuming the necessary information
> was
> > encoded in ACPI Tables. But I cannot find any mention of this device in
> the
> > acpi tables exposed by the kernel.
> >
> > I tried grepping through all the ACPI tables in
> /sys/firmware/acpi/tables.
> > I was hoping to find some string that could identify the corresponding
> > kernel drivers. But there are no hits for "lis". I suppose string based
> > literals are not the way acpi works like in kernel device-driver
> matching.
> > The driver in question is  drivers/misc/lis3lv02d/lis3lv02d.c
> >
> > So what exactly in the ACPI triggered the kernel module lis3lv02d to be
> > loaded ?
>
> It seems to me this is an I2C device so the following alias could load it:
>
> modules.alias:alias i2c:lis3lv02d lis3lv02d_i2c
>

Apparently it could be both I2C or SPI, as I find lis3lv02d_spi.c as well.
I don't really know if this device sits on I2C bus or SPI.


> --
> Valentin
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>


-- 

Thanks and Regards,
*Aurabindo J*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20190106/e89ba235/attachment.html>