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 8DF12C43387 for ; Sun, 6 Jan 2019 08:54:13 +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 3317E218FC for ; Sun, 6 Jan 2019 08:54:13 +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="qjTZzrl6" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3317E218FC 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 1gg4Br-0004kz-0p; Sun, 06 Jan 2019 03:53:51 -0500 Received: from mail-oi1-x22e.google.com ([2607:f8b0:4864:20::22e]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1gg4Bo-0004kt-Vf for kernelnewbies@kernelnewbies.org; Sun, 06 Jan 2019 03:53:49 -0500 Received: by mail-oi1-x22e.google.com with SMTP id t204so33632918oie.7 for ; Sun, 06 Jan 2019 00:53:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=agzwDPvxO4R6Knyxphn4GZ/g40QO2bQuzetnEXHAvYQ=; b=qjTZzrl6cx6Cym4jnHVUocwFx0gNLGi667IcF2GpoypuZDP3XRYlM/SwOyOhPOo+X5 j3ilRqgchHJCO2aYAplBaS1jESbiCXJ/ngD5rShEr+gNFg+kOcqiiKktTJZZp7JzfdUm st37avVrV4/CqBCKzVTQZshxX4daYCxIxn/EpYlRcvDoJgHhIAgKzkO4hYPVVTMsq+Xy k8Vxw6rtLRPWhzdg2fJ0Ev9mkXPS2cvcIx5GdJv1nBdKrRYS5JW1LR3IZKlrGke2W7Le ort2XQ/ekB1r/I4IoVRmkPlmzYm6NYJiXc8F//ZEmJ6A8HKsAeKm2Yg52ylgKD+X34dF M74g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=agzwDPvxO4R6Knyxphn4GZ/g40QO2bQuzetnEXHAvYQ=; b=NfgGamDua60knFTbbIj6uss+UK782Dws1alf5NlRNUf/6+l+m3s6fQHXOmjnkdjjf+ e58+y+1OzUAPUr48uTBWcc+5vCp/tabf+xwzXpJs4vLm3pLRCDMndyKYlnQfbLsBVOC8 DgL1C4GZn/1TyWj5Bv3hi1zs5sIqJ7d6bJVNVDYe1VSMvbl/zFNz5v7lMBQCqUYGd80U 8c7t6Pihm8J4a8FpdXxkXQCIiMT2MjWPUntPnTMeqQxCZyGJ+bd8q7jXB9W6m7GcWh/K v6UO/L3/asvi7MaL93wXhMbQZuy0DWFQynOcj8IjAVuX4NdcMC0zYHYQ+EUYSWkx2n/l 6Kfw== X-Gm-Message-State: AJcUuke9Uhti1vpb8odxrts2YhLVf23wnHYTfducqK9tR6NRIqyHgSBz SvasFJnsm0Pk2BuxJgwgBZ1imEJqO/LAybxQaZPEUK5C X-Google-Smtp-Source: ALg8bN5q/tISeiO+rnn3O4ov0Cqsnb1T2TYy6Qiev1gE0vACFC/tTB/OSXAnzgkwKdMX/WmthWfqnKa2pFBmAkPn+B8= X-Received: by 2002:aca:ba83:: with SMTP id k125mr5355307oif.159.1546764765648; Sun, 06 Jan 2019 00:52:45 -0800 (PST) MIME-Version: 1.0 From: Jay Aurabind Date: Sun, 6 Jan 2019 14:22:34 +0530 Message-ID: Subject: The Kernel knows. But how ? Did the acpi make a secret dead drop ? To: 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="===============3860846590153863757==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============3860846590153863757== Content-Type: multipart/alternative; boundary="000000000000685d05057ec63c2f" --000000000000685d05057ec63c2f Content-Type: text/plain; charset="UTF-8" Hi, 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 ? -- Thanks and Regards, *Aurabindo J* --000000000000685d05057ec63c2f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

The subject line might be a bit drama= tic, 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 e= ncoded in ACPI Tables. But I cannot find any mention of this device in the = acpi tables exposed by the kernel.

I tried greppin= g through all the ACPI tables in /sys/firmware/acpi/tables. I was hoping t= o find some string that could identify the corresponding kernel drivers. Bu= t there are no hits for "lis". I suppose string based literals ar= e not the way acpi works like in kernel device-driver matching. The driver = in question is=C2=A0 drivers/misc/lis3lv02d/lis3lv02d.c

<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ">So what exactly in the ACPI triggered the kernel module lis3lv02d to be l= oaded ?

--

Thanks and Regards,
Aurabindo J
<= /div>
--000000000000685d05057ec63c2f-- --===============3860846590153863757== 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 --===============3860846590153863757==--