From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AA46BC43387 for ; Sun, 6 Jan 2019 12:49:25 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3D08020878 for ; Sun, 6 Jan 2019 12:49:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="hSOh37PK" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3D08020878 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=fail smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.91) (envelope-from ) id 1gg7rR-0005xp-Hq; Sun, 06 Jan 2019 07:49:01 -0500 Received: from mail-ot1-x32f.google.com ([2607:f8b0:4864:20::32f]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1gg7rO-0005xj-Gq for kernelnewbies@kernelnewbies.org; Sun, 06 Jan 2019 07:48:58 -0500 Received: by mail-ot1-x32f.google.com with SMTP id i20so35716354otl.0 for ; Sun, 06 Jan 2019 04:48:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BGjT6Qtfa729+XSe/yocYefoX2Eqd3qXSsQpmUqAFhI=; b=hSOh37PKipiyaI4L0eq6ub+UZ3wVxD0KipEehT3hgvrO7lYseXlupw6gsc+UaGsXs+ ylZk4FoTIjbm68FIyx1HelwcEA5Kr+1Ng+lw3EpqT9+5kj4P3Ihtusz1HBQJLGr+p5h0 jjLeNQljiHXJC/KHN9rEFT6ZLsEKtZORDBuAA3wcoCio3sFL/EOdIRVJpnsdipi8yYH/ kdrYieRom+smRZJ6RYnXZqcKqYBaVbqqtO7EdoaLJnx+Dpfr4mLasu4Napp2Y2jDyylN 1B8ttcM04xCW6fMeDfwFmTkPmzLA/+uDd6czCOEyIWOIuwN5uWYYw/RkmGPusr6JypnF 4zPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BGjT6Qtfa729+XSe/yocYefoX2Eqd3qXSsQpmUqAFhI=; b=r1+YRYgY0xZehAfPYFGSyJmEvsC8uYi/p38vejzAodeKSzIJUiert8mnU8zodXheHJ /P71LlEoY4shA3W20T79LOiBPzeKDoCf0I4cYnxODURP1kaF2cEP1+Zh7CRh2bVib/G9 KaKCFDeytvwxNyMXJHtmxX4T8oFmbkjyP5uhjVfnHpy0N/SzXvcyR/Lj0npRafJ8kH9C YUcFrgwPvdfaxceTEIYaS8cM3Km6asdZpKZ1KdpL/ERh/P0zVQAYx+U98orivyfYyZxc ofic3JgSa82WHFsffMpytZs7VlhRazQNLBO2+LS4ONSQt3cZN+zf9IDjMSdK8tURFzVW dnlQ== X-Gm-Message-State: AJcUukcwWW4/69aXIpo3e3EShNVifO/bSS/sfs87OHUhKuPbVMz0/o76 RbSvzDCMEqZHpWu/Qh/tgkMlW8BbJ+yBjFYNR9IT1xAu X-Google-Smtp-Source: ALg8bN6sg4fwlpevP8eYaK6eM+yxEVd8Fzl+bK13fsdbxe3rF0uyINdaMPNC3mSld+S8pEWjamwZ8OzSpxSxSpjbHKc= X-Received: by 2002:a9d:2227:: with SMTP id o36mr40775546ota.29.1546778876389; Sun, 06 Jan 2019 04:47:56 -0800 (PST) MIME-Version: 1.0 References: <20190106111914.GF2250@gavran.carpriv.carnet.hr> In-Reply-To: <20190106111914.GF2250@gavran.carpriv.carnet.hr> From: Jay Aurabind Date: Sun, 6 Jan 2019 18:17:44 +0530 Message-ID: Subject: Re: The Kernel knows. But how ? Did the acpi make a secret dead drop ? To: Valentin Vidic Cc: kernelnewbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6694429878498825323==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============6694429878498825323== Content-Type: multipart/alternative; boundary="000000000000792dfe057ec98522" --000000000000792dfe057ec98522 Content-Type: text/plain; charset="UTF-8" On Sun, 6 Jan 2019 at 16:49, Valentin Vidic 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* --000000000000792dfe057ec98522 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, 6 Jan 2019 at 16:49, Valentin Vidic <<= a href=3D"mailto:Valentin.Vidic@carnet.hr">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 informatio= n was
> encoded in ACPI Tables. But I cannot find any mention of this device i= n the
> acpi tables exposed by the kernel.
>
> I tried grepping through all the ACPI tables in /sys/firmware/acpi/tab= les.
> I was hoping to find some string that could identify the corresponding=
> kernel drivers. But there are no hits for "lis". I suppose s= tring based
> literals are not the way acpi works like in kernel device-driver match= ing.
> The driver in question is=C2=A0 drivers/misc/lis3lv02d/lis3lv02d.c
>
> So what exactly in the ACPI triggered the kernel module lis3lv02d to b= e
> loaded ?

It seems to me this is an I2C device so the following alias could load it:<= br>
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 o= n I2C bus or SPI.


--
Valentin

_______________________________________________
Kernelnewbies mailing list
Kernel= newbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailma= n/listinfo/kernelnewbies


--

Thanks and Regards,
Aurabindo J
--000000000000792dfe057ec98522-- --===============6694429878498825323== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============6694429878498825323==--