From: Jay Aurabind <jay.aurabind@gmail.com>
To: Valentin Vidic <Valentin.Vidic@carnet.hr>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: The Kernel knows. But how ? Did the acpi make a secret dead drop ?
Date: Sun, 6 Jan 2019 18:17:44 +0530 [thread overview]
Message-ID: <CAOsEZoiL=1+Rpya89nZ9G6FsP8yeR82-4zRoQ7q2r+ouLFLMSQ@mail.gmail.com> (raw)
In-Reply-To: <20190106111914.GF2250@gavran.carpriv.carnet.hr>
[-- Attachment #1.1: Type: text/plain, Size: 1502 bytes --]
On Sun, 6 Jan 2019 at 16:49, Valentin Vidic <Valentin.Vidic@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@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
Thanks and Regards,
*Aurabindo J*
[-- Attachment #1.2: Type: text/html, Size: 2915 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-01-06 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 8:52 The Kernel knows. But how ? Did the acpi make a secret dead drop ? Jay Aurabind
2019-01-06 11:16 ` Greg KH
2019-01-06 11:19 ` Valentin Vidic
2019-01-06 12:47 ` Jay Aurabind [this message]
2019-01-06 13:00 ` Valentin Vidic
2019-01-06 13:28 ` Jay Aurabind
2019-01-06 14:07 ` Valentin Vidic
2019-01-06 15:02 ` Jay Aurabind
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOsEZoiL=1+Rpya89nZ9G6FsP8yeR82-4zRoQ7q2r+ouLFLMSQ@mail.gmail.com' \
--to=jay.aurabind@gmail.com \
--cc=Valentin.Vidic@carnet.hr \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).