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=-2.3 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, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS 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 DFEC2C433E0 for ; Sun, 14 Jun 2020 10:31:02 +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 8FD8E204EA for ; Sun, 14 Jun 2020 10:31:02 +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="HTO66cNF" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8FD8E204EA Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.93) (envelope-from ) id 1jkPum-0003Pi-Bc for kernelnewbies@archiver.kernel.org; Sun, 14 Jun 2020 06:31:00 -0400 Received: from mail-ua1-x92b.google.com ([2607:f8b0:4864:20::92b]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1jkPsu-0001GY-St for kernelnewbies@kernelnewbies.org; Sun, 14 Jun 2020 06:29:04 -0400 Received: by mail-ua1-x92b.google.com with SMTP id c9so4672528uao.11 for ; Sun, 14 Jun 2020 03:29:04 -0700 (PDT) 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=3Us2weUpcqMyC8OCcCYDRmhTNjYd5ZUodqKrydo/+qg=; b=HTO66cNFI/MzFlsuOgb5KhMANH3CABbmmkatrQjAt23gNRboEuFwlHHd2XFBVgUQQk I0VSTndPJMDxe6IqSde97RDzm6/LLQE4ShMPXWryWXVxcrRE2mD46O4orB50Wx3ZJFs4 M3M5zRGLyhHyJL6IFAFyZWSVe5r6r2esqH2Yye2BmVZILCzfiTkeO80R9TDsyhKXrC9j RGFxB511okU8AA9JNb2BZ7gcp52XlKcU6toLPTBfQNsekXPqEofi4TnZdHx2ShJsEFOi JfFXy7Um/9pft6dpIeGqRm9VhcImrzHhG6t5xRO3zt4aJE/9ZrMHsx/QiKSC5Mljyikx Fy4A== 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=3Us2weUpcqMyC8OCcCYDRmhTNjYd5ZUodqKrydo/+qg=; b=RSH1qrdqGplNicXwqzl+nyX5XMQRD93tcO2gsGW0tXXKUouhdR9u43JqCCk2hJYkHJ xY6AR6sHst5AUaxtxWy5QvMNmv01muNSUs+CH8HMqzCl1TWz9wh8yAH0KUlLHZiHHssa R/zvFsU1jaNltprGOnna3DnjfHXpYHnSIkjunxUFbTZevfRqVU/yBpOZixFMIX8dfY2R +4kZM7B/CxiGszj0cBVr97w7PCB/iDww9AqoTlQ/7HCwfBENzOv4YICEQgwaXxDhrNYU WZFRoOIIGbVHW5//KG6zdKMuRn5WIvKsXjeqrTSOcizBOIzcT57ESRuGq7SeYXnRKaBX zX4w== X-Gm-Message-State: AOAM53319IybQ9+UELPZUVGl8OfO/PCnrRI+pubFIyNHKnP66jQmuiZP TuUz4W3xBrIaK0Sk31UWpU10q3NYme9u3iJsAbgDIiXv1Cw= X-Google-Smtp-Source: ABdhPJwn+ZMHgzgmlaQv6hyCptEXwiZQ+JhjAjsfllEskshazahmrEiCFRw2p9CtNVzf5ukOvvMurJFryRavFG29rMo= X-Received: by 2002:a9f:3049:: with SMTP id i9mr15192597uab.113.1592130480745; Sun, 14 Jun 2020 03:28:00 -0700 (PDT) MIME-Version: 1.0 From: Sergey Ivanov Date: Sun, 14 Jun 2020 13:27:49 +0300 Message-ID: Subject: issue with ASUS Fan maximal mode To: kernelnewbies@kernelnewbies.org 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="===============6054500933123269656==" Errors-To: kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org --===============6054500933123269656== Content-Type: multipart/alternative; boundary="000000000000bdaf4105a808c3b7" --000000000000bdaf4105a808c3b7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi there. I have a headache with linux bug https://bugzilla.kernel.org/show_bug.cgi?id=3D153281 and i'm one from many others that still suffered from the described issue. Personally i was able to move forward a bit. In particular, 1) with a great soft that manipulates with fan speed ranges https://github.com/dominiksalvet/asus-fan-control/issues/43 i was able to understand how maximal mode is activated at very low level in the so-called embedded controller in addresses 0x0521 and 0x0522. 2) It seems i understand that there is another driver/hardware mode that activates maximal mode eternally. 3) I disassembled my dsdt tables and found no more destructive code that could change maximal mode back https://github.com/icegood/my_dsdts =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D So, i'm interest in people here who could help me cruising in kernel sources to understand who else can communicate with an embedded controller. For now, I'm interested how driver asus-nb-wmi registers it's controlling chipset to hwmon so /sys/devices/platform/asus-nb-wmi/hwmon/hwmon5 node is created. >From sensors i see that it is a asus-isa-0000 Adapter: ISA adapter cpu_fan: 1900 RPM temp1: +53.0=C2=B0C and i wonder how it registered. --=20 Kind regards, Sergey Ivanov --000000000000bdaf4105a808c3b7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi there.
and i'm one f= rom many others that still suffered from the described issue. Personally i = was able to move forward a bit. In particular,
1) with a=C2= =A0 great soft that manipulates with fan speed ranges
https://github.com/d= ominiksalvet/asus-fan-control/issues/43
i was able to underst= and how maximal mode is activated at very low level in the so-called embedd= ed controller in addresses
0x0521 and 0x0522.
2) It see= ms i understand that there is another driver/hardware mode that activates m= aximal mode eternally.

3) I disassembled my ds= dt tables and found no more destructive code that could change maximal mode= back
https://github.com= /icegood/my_dsdts
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
So, i'm interest in people here who could help me cruising= in kernel sources to understand who else can communicate with an embedded = controller. For now, I'm interested how driver asus-nb-wmi registers it= 's controlling chipset to hwmon so
/sys/devices/platform/asus-nb-wm= i/hwmon/hwmon5
node is created.
From sensors i = see that it is a
asus-isa-0000
Adapter: ISA adapter
cpu_fan: =C2= =A0 =C2=A0 1900 RPM
temp1: =C2=A0 =C2=A0 =C2=A0 =C2=A0+53.0=C2=B0C
<= br>
and i wonder how it registered.

= --
Kind regards,
Sergey I= vanov
--000000000000bdaf4105a808c3b7-- --===============6054500933123269656== 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 --===============6054500933123269656==--