Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp4930810pxu; Tue, 13 Oct 2020 10:22:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxTWZttUhZAyFvjAGvP7buoHpLyAC0vcJ/zUtXuu/X4d4Le59wNXYdRcHhUt6jFKrd9dD02 X-Received: by 2002:aa7:d782:: with SMTP id s2mr598699edq.111.1602609759958; Tue, 13 Oct 2020 10:22:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602609759; cv=none; d=google.com; s=arc-20160816; b=WzPKU3AP4cGpgTSBu8zJSkNC9o1a2GLXmLO8SykN+BpC8aIOj9EmlSIWaHGU356IF+ uEVV2PV+UsO4aNFOMpGFAQGEfb++mMvpgZeGgYu7mrg/2Ikhjnwz6vwaBrikSkznjsPJ CqEayKKvM0rrlr8WAZ64xrEzg3d7gEVB7WSYJ1mlGk2VhKES4esLZgbYFNHsqincgDCT FRAyp/g6PgkCwvCQpoC5S1CdLf7aqrEZSHgwXjhV45XibpiftuSl17lGG17NNedNXE2H /rNk9fxImIT62+P387kWslsqa+SefxcPx7Bijh2flf3+hGXVGAToGQym0TO+d/UNslLL 7Ftw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=3SSjaCQdRGMbRZ/PKfWkgAVprtJhUC9fQa9aal9xkZg=; b=ndxpKdAhT+w5h6nXeptuzZMOsnU77aDHtkEIgt5W80jJSyso1dPMObA4R396LoOrvX qhSMIZ/ITE7vGXNrZi11L4XMMnbk49JncWsBBM6mHzBbULL9ibe03B0frkiFlbeyh7ZU OFkp1Ye78mhANEIXS/FpLET/DG+OMheqVJlwuvZfd+03k6fd16DOSyAFu2whls2I3HAB MEtrK7eRtjYTbhP4l+JHdTsvxyw8g4Ob0RcgI444YmttfCrRTWP75aVVViF1KDig9JDy 9bHDApREgLvfr/6YukTwzLQcAnjg85Z3WZOnXmSmcOeEtcKMaZB1C/YPeKXttn7XREyj BOXQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o4si208962ejx.558.2020.10.13.10.22.17; Tue, 13 Oct 2020 10:22:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389059AbgJMPAl (ORCPT + 99 others); Tue, 13 Oct 2020 11:00:41 -0400 Received: from mx3.molgen.mpg.de ([141.14.17.11]:43963 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2388871AbgJMPAk (ORCPT ); Tue, 13 Oct 2020 11:00:40 -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 2FC6920647116; Tue, 13 Oct 2020 17:00:37 +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> <7921b792-c99a-659c-730f-ecb25cb7f04b@molgen.mpg.de> From: Paul Menzel Message-ID: <082dfba3-6187-7081-6a8c-8c38a3a95b19@molgen.mpg.de> Date: Tue, 13 Oct 2020 17:00:37 +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-kernel@vger.kernel.org Dear Rafael, dear Dmitry, Am 12.10.20 um 13:00 schrieb Rafael J. Wysocki: > On Mon, Oct 12, 2020 at 12:50 PM Paul Menzel wrote: >> Am 12.10.20 um 12:39 schrieb Rafael J. Wysocki: >>> On Sun, Oct 11, 2020 at 1:08 AM Paul Menzel wrote: >>>> 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? > > Inspecting the ACPI tables from the system in question could help you > to find out whether or not IOST really is a field in an operation > region, but its initial value may not be possible to determine this > way. > >> Is there a Linux kernel parameter, that would print it? > > Not that I know of. I created an issue in the Linux kernel bugtracker [1] and attached the output of `acpidump` there. Could If ((IOST & 0x4000)) versus If ((IOST & 0x0400)) be a typo? Kind regards, Paul [1]: https://bugzilla.kernel.org/show_bug.cgi?id=209657