From: Sergey Ivanov <icegood1980@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: issue with ASUS Fan maximal mode
Date: Sun, 14 Jun 2020 13:27:49 +0300 [thread overview]
Message-ID: <CAJCbrz7rwnERhQee70jTQ4y-0i-7rps79YGvHVPwVADStNUZDg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1272 bytes --]
Hi there.
I have a headache with linux bug
https://bugzilla.kernel.org/show_bug.cgi?id=153281
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
================
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°C
and i wonder how it registered.
--
Kind regards,
Sergey Ivanov
[-- Attachment #1.2: Type: text/html, Size: 1834 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
reply other threads:[~2020-06-14 10:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJCbrz7rwnERhQee70jTQ4y-0i-7rps79YGvHVPwVADStNUZDg@mail.gmail.com \
--to=icegood1980@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).