From: Guenter Roeck <linux@roeck-us.net>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: andy.shevchenko@gmail.com, pauk.denis@gmail.com,
Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC
Date: Tue, 11 Jan 2022 08:33:27 -0800 [thread overview]
Message-ID: <a2abe48e-3547-be08-5f4e-1fb6fd47faef@roeck-us.net> (raw)
In-Reply-To: <20220111160900.1150050-2-eugene.shalygin@gmail.com>
On 1/11/22 8:08 AM, Eugene Shalygin wrote:
> This driver provides the same data as the asus_wmi_ec_sensors driver
> (and gets it from the same source) but does not use WMI, polling
> the ACPI EC directly.
>
> That provides two enhancements: sensor reading became quicker (on some
> systems or kernel configuration it took almost a full second to read
> all the sensors, that transfers less than 15 bytes of data), the driver
> became more flexible. The driver now relies on ACPI mutex to lock access
> to the EC in the same way as the WMI code does.
>
> Signed-off-by: Eugene Shalygin <eugene.shalygin@gmail.com>
Please version all patches, not just the intro. As it is, the version doesn't
show up in patchwork, which is confusing.
Guenter
next prev parent reply other threads:[~2022-01-11 16:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 16:08 PATCH v3 ASUS EC Sensors Eugene Shalygin
2022-01-11 16:08 ` [PATCH 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC Eugene Shalygin
2022-01-11 16:33 ` Guenter Roeck [this message]
2022-01-11 17:04 ` Guenter Roeck
2022-01-11 17:22 ` Eugene Shalygin
2022-01-11 18:43 ` Guenter Roeck
2022-01-11 18:52 ` Eugene Shalygin
2022-01-11 19:15 ` Guenter Roeck
2022-01-11 19:18 ` Eugene Shalygin
2022-01-11 16:08 ` [PATCH 2/3] hwmon: (asus-ec-sensors) update documentation Eugene Shalygin
2022-01-11 16:08 ` [PATCH 3/3] hwmon: (asus_wmi_ec_sensors) remove the driver Eugene Shalygin
2022-01-11 16:36 ` Guenter Roeck
2022-01-11 16:38 ` PATCH v3 ASUS EC Sensors Guenter Roeck
2022-01-11 16:59 ` Eugene Shalygin
-- strict thread matches above, loose matches on Subject: below --
2021-12-17 16:43 PATCH v2 " Eugene Shalygin
2021-12-17 16:43 ` [PATCH 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC Eugene Shalygin
2021-12-17 21:52 ` Guenter Roeck
2021-12-17 22:33 ` Eugene Shalygin
2021-12-17 23:47 ` Guenter Roeck
2021-12-16 20:53 Eugene Shalygin
2021-12-16 21:27 ` Andy Shevchenko
2021-12-16 22:04 ` Denis Pauk
2021-12-16 22:58 ` Eugene Shalygin
2021-12-18 18:48 ` Denis Pauk
2021-12-17 0:07 ` Eugene Shalygin
2021-12-17 4:35 ` kernel test robot
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=a2abe48e-3547-be08-5f4e-1fb6fd47faef@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andy.shevchenko@gmail.com \
--cc=eugene.shalygin@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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