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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AA7F8C433FE for ; Wed, 23 Nov 2022 23:01:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229515AbiKWXBg (ORCPT ); Wed, 23 Nov 2022 18:01:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53096 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229471AbiKWXBf (ORCPT ); Wed, 23 Nov 2022 18:01:35 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9490359170 for ; Wed, 23 Nov 2022 15:01:33 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 26A68B82566 for ; Wed, 23 Nov 2022 23:01:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id C1157C4FEB7 for ; Wed, 23 Nov 2022 23:01:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1669244490; bh=Abb3dVynIPo+tte4Vi2sd5o3H7kKE38yxw6YDe+t4vM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=BQBoBHrJPeEjlifVuZuMtAt3/eBwaNDCIv6LylK/11H+8N7+xYuNONu5DSz/uRQFr Pw8T6hEW5qCIXu+H1zKgPcNavr+NsT79F6kyLCkzKG6dgtKdxcRPUokJh3xi/v43nl /yDB7MnxKWKTc0lFTFifm+t6OXQDf2SYmgUGAuBqENYtIz/pjIHJqbP9RwOgkDXiaD VbIXsq9AqlKrB/8hzohl13h4FTAWF244YVz7bG6BkXISgA/W/oU792u7XH1XraYjMF zOfbz8v0uUETUBoOF/1phprzBxAPWcIk/c7hJkHrmkFUqpoMhpXmIku3Dbr2A1SqmF b/Q2BADnfXcHQ== Received: by aws-us-west-2-korg-bugzilla-1.web.codeaurora.org (Postfix, from userid 48) id B29ECC433E6; Wed, 23 Nov 2022 23:01:30 +0000 (UTC) From: bugzilla-daemon@kernel.org To: platform-driver-x86@vger.kernel.org Subject: [Bug 204807] Hardware monitoring sensor nct6798d doesn't work unless acpi_enforce_resources=lax is enabled Date: Wed, 23 Nov 2022 23:01:28 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo drivers_platform_x86@kernel-bugs.osdl.org X-Bugzilla-Product: Drivers X-Bugzilla-Component: Platform_x86 X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: high X-Bugzilla-Who: pauk.denis@gmail.com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: CODE_FIX X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: drivers_platform_x86@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: platform-driver-x86@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=3D204807 --- Comment #275 from Denis Pauk (pauk.denis@gmail.com) --- (In reply to Slawomir Stepien from comment #274) > (In reply to Slawomir Stepien from comment #273) > > (In reply to Denis Pauk from comment #272) > > > (In reply to Slawomir Stepien from comment #271) > > > > Created attachment 303265 [details] > > > > Add support for ROG STRIX B660-I GAMING WIFI > > > >=20 > > > > This adds support for ROG STRIX B660-I GAMING WIFI into the "Asus W= MI > for > > > > nct6775 v6.0 base (2022.11.12)" patch. > > >=20 > > > Thank you! I will add your code to the next patch version. > > >=20 > > > Just for recheck, could you please share error place on init when you > added > > > your board to asus_acpi_boards(x670 generation methods) or > > > asus_wmi_boards(b550/x570 generation methods)? Are both of methods of > > access > > > failed?=20 > > >=20 > > > I have hoped B660 boards have same access method as x670 boards at le= ast > > :-( > >=20 > > [93233.798384] nct6775: Can't read ChipID by Asus WMI. > > [93233.798386] nct6775: No dmi definition `ROG STRIX B660-I GAMING > > WIFI`:`ASUSTeK COMPUTER INC.` > > [93233.798446] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290 > > [93233.798449] ACPI Warning: SystemIO range > > 0x0000000000000295-0x0000000000000296 conflicts with OpRegion > > 0x0000000000000290-0x0000000000000299 (\RMTW.SHWM) (20220331/utaddress-= 204) > > [93233.798452] ACPI: OSL: Resource conflict; ACPI support missing from > > driver? >=20 > But if I add the board to the asus_acpi_boards, it works but with: >=20 > [93515.558164] nct6775: Using Asus ACPI to access 0xc1 chip. > [93515.558166] nct6775: No dmi definition `ROG STRIX B660-I GAMING > WIFI`:`ASUSTeK COMPUTER INC.` > [93515.558229] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290 >=20 > So I guess this is a better approach for my case? It should be, its near to correct way as its designed by ASUS. Its not clear for now how to make such calls by WMI, i suppose that they have changed WMI method ID to some different or hide it behind other methods.=20=20 Look to the X670 patch discussion: https://patchwork.kernel.org/project/linux-hwmon/patch/20221018173428.71080= -1-ahmad@khalifa.ws/ --=20 You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.=