From: Eugene Shalygin <eugene.shalygin@gmail.com>
To: Denis Pauk <pauk.denis@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Oleksandr Natalenko <oleksandr@natalenko.name>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Jean Delvare <jdelvare@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-hwmon@vger.kernel.org
Subject: Re: [ASUS EC Sensors v8 0/3]
Date: Thu, 3 Feb 2022 21:55:34 +0100 [thread overview]
Message-ID: <CAB95QAT2iZexNF__dwJQHWoeFACcCMPGFGQQyF_9weATkfeJ+A@mail.gmail.com> (raw)
In-Reply-To: <20220203222310.6a025c5d@netbook-debian>
> I have also retested code, it works for my case.
>
> Tested-by: Denis Pauk <pauk.denis@gmail.com>
Thanks!
> What about other B550/X570 boards?
>
> We have such candidates with same WMI methods in nct6775:
> "ROG STRIX B550-A GAMING",
> "ROG STRIX B550-E GAMING",
> "ROG STRIX B550-F GAMING",
> "ROG STRIX B550-F GAMING (WI-FI)",
> "ROG STRIX B550-I GAMING",
>
> B550-A does not support asus-wmi-ec-interface("ERROR: Can't get value
> of subfeature fan1_input: I/O error"), but what about others?
I don't have DSDT for these boards, but most of them have the
T_Sensor, according to the specs at the ASUS web-site, so, probably,
their EC should report something, because most of their boards report
T_Sensor reading via the EC.
Best regards,
Eugene
next prev parent reply other threads:[~2022-02-03 20:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 1:56 [ASUS EC Sensors v8 0/3] Eugene Shalygin
2022-01-24 1:56 ` [ASUS EC Sensors v8 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC Eugene Shalygin
2022-01-25 8:49 ` Oleksandr Natalenko
2022-01-24 1:56 ` [ASUS EC Sensors v8 2/3] hwmon: (asus-ec-sensors) update documentation Eugene Shalygin
2022-01-25 8:48 ` Oleksandr Natalenko
2022-01-24 1:56 ` [ASUS EC Sensors v8 3/3] hwmon: deprecate asis_wmi_ec_sensors driver Eugene Shalygin
2022-01-25 8:47 ` Oleksandr Natalenko
2022-02-02 23:58 ` [ASUS EC Sensors v8 0/3] Eugene Shalygin
2022-02-03 1:10 ` Guenter Roeck
2022-02-03 1:16 ` Eugene Shalygin
2022-02-03 3:41 ` Guenter Roeck
2022-02-03 3:48 ` Eugene Shalygin
2022-02-03 7:09 ` Oleksandr Natalenko
2022-02-03 18:54 ` Guenter Roeck
2022-02-03 20:01 ` Eugene Shalygin
2022-02-03 20:24 ` Denis Pauk
2022-02-03 20:55 ` Eugene Shalygin [this message]
2022-02-04 20:13 ` Eugene Shalygin
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=CAB95QAT2iZexNF__dwJQHWoeFACcCMPGFGQQyF_9weATkfeJ+A@mail.gmail.com \
--to=eugene.shalygin@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oleksandr@natalenko.name \
--cc=pauk.denis@gmail.com \
/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).