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=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 0E56DC43467 for ; Mon, 12 Oct 2020 10:50:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C592C21655 for ; Mon, 12 Oct 2020 10:50:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387822AbgJLKup (ORCPT ); Mon, 12 Oct 2020 06:50:45 -0400 Received: from mx3.molgen.mpg.de ([141.14.17.11]:54087 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2387725AbgJLKuo (ORCPT ); Mon, 12 Oct 2020 06:50:44 -0400 Received: from [141.14.220.45] (g45.guest.molgen.mpg.de [141.14.220.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id 0C1B520646219; Mon, 12 Oct 2020 12:50:41 +0200 (CEST) Subject: Re: i8042_init: PS/2 mouse not detected with ACPIPnP/PnPBIOS To: "Rafael J. Wysocki" Cc: Dmitry Torokhov , "Rafael J. Wysocki" , Len Brown , linux-input@vger.kernel.org, LKML , ACPI Devel Maling List , Hans de Goede References: <1a69c5bc-ccc4-68db-7871-af05a70052c9@molgen.mpg.de> <20201007221628.GW1009802@dtor-ws> From: Paul Menzel Message-ID: <7921b792-c99a-659c-730f-ecb25cb7f04b@molgen.mpg.de> Date: Mon, 12 Oct 2020 12:50:40 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org Dear Rafael, Am 12.10.20 um 12:39 schrieb Rafael J. Wysocki: > On Sun, Oct 11, 2020 at 1:08 AM Paul Menzel wrote: >> >> Dear Dmitry, dear Rafael, dear Len, >> >> >> Am 08.10.20 um 00:16 schrieb Dmitry Torokhov: >> >>> On Wed, Oct 07, 2020 at 11:18:41PM +0200, Paul Menzel wrote: >> >>>> On the Asus F2A85-M PRO Linux 5.9-rc8 (and previous versions) does not >>>> recognize a plugged in PS/2 mouse using the Plug & Play method. The PS/2 >>>> keyboard is detected fine, and using `i8042.nopnp`, the PS/2 mouse also >>>> works. >>>> >>>>> [ 1.035915] calling i8042_init+0x0/0x42d @ 1 >>>>> [ 1.035947] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 >>>>> [ 1.035948] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp >>>>> [ 1.036589] serio: i8042 KBD port at 0x60,0x64 irq 1 >>>>> [ 1.036621] initcall i8042_init+0x0/0x42d returned 0 after 687 usecs >>>> >>>> But, the DSDT includes the “mouse device”. From >>>> >>>> acpidump > dump.bin; acpixtract dump.bin; iasl -d *dat; more dsdt.dsl >>>> >>>> we get >>>> >>>> Device (PS2M) >>>> { >>>> Name (_HID, EisaId ("PNP0F03") /* Microsoft PS/2-style Mouse */) // _HID: Hardware ID >>>> Name (_CID, EisaId ("PNP0F13") /* PS/2 Mouse */) // _CID: Compatible ID >>>> Method (_STA, 0, NotSerialized) // _STA: Status >>>> { >>>> If ((IOST & 0x4000)) >>>> { >>>> Return (0x0F) >>>> } >>>> Else >>>> { >>>> Return (Zero) >>>> } >>>> } >>>> >>>> and the identifiers PNP0F03 and PNP0F13 are both listed in the array >>>> `pnp_aux_devids[]`. But adding print statements to `i8042_pnp_aux_probe()`, >>>> I do not see them, so the function does not seem to be called. >>> >>> My guess is that _STA returns 0 indicating that the device is not >>> present. I would try tracking where IOST is being set and figuring out >>> why it does not have mouse bit enabled. >> >> Does the ACPI subsystem allow to track, how ACPI variables(?) like IOST >> are read and set? > > My guess would be that IOST is a field in an operation region which > would indicate that it is initialized by the bootstrap part of the > BIOS. Thank you for your answer. But how can I verify that? Is there a Linux kernel parameter, that would print it? Kind regards, Paul