public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: andy.shevchenko@gmail.com, pauk.denis@gmail.com,
	Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>,
	linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org
Subject: Re: PATCH v4 ASUS EC Sensors
Date: Sun, 16 Jan 2022 20:28:59 +0100	[thread overview]
Message-ID: <2613330.mvXUDI8C0e@natalenko.name> (raw)
In-Reply-To: <20220111180347.1245774-1-eugene.shalygin@gmail.com>

Hello.

On úterý 11. ledna 2022 19:03:43 CET Eugene Shalygin wrote:
> This patchset replaces the HWMON asus_wmi_ec_sensors driver with
> an implementation that does not use WMI but queries the embedded
> controller 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 fexible. The driver now relies on ACPI mutex to lock access
> to the EC, in the same way as the WMI DSDT code does.
> 
> Chenges in v5:
>  - Place the sensors bitset directly into the driver_data field of the
> 	 dmi_system_id struct.
>  - Replace doc comments with regular ones.

BTW, is this OK:

```
[   11.104396] asus-ec-sensors PNP0C09:00: board has 6 EC sensors that span 7 registers
[   11.104400] asus-ec-sensors PNP0C09:00: hwmon: 'asus-ec-sensors' is not a valid name attribute, please fix
```

?

> 
> Changes in v4:
>  - Deprecate the wmi driver rather than removing it.
> 
> Changes in v3:
>  - Remove BIOS version checks and BIOS version dependent mutex path.
> 
> Changes in v2:
>  - Replace sensor flags enum with bitset
>  - Replace module init/probe functions with module_platform_driver_probe
>    and ask the platform drivers framework to load the driver when ACPI
>    EC is found (ACPI ID "PNP0C09").
>  - Extend board data with BIOS version attribute for the mutex path to be
>    BIOS version dependent.
>  - Add module parameter to override the mutex path.

Thanks.

-- 
Oleksandr Natalenko (post-factum)



  parent reply	other threads:[~2022-01-16 19:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 18:03 PATCH v4 ASUS EC Sensors Eugene Shalygin
2022-01-11 18:03 ` [PATCH v5 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC Eugene Shalygin
2022-01-11 18:03 ` [PATCH v5 2/3] hwmon: (asus-ec-sensors) update documentation Eugene Shalygin
2022-01-11 18:03 ` [PATCH v5 3/3] hwmon: deprecate asis_wmi_ec_sensors driver Eugene Shalygin
2022-01-12 21:51   ` Oleksandr Natalenko
2022-01-13  2:51     ` Guenter Roeck
2022-01-15 12:32       ` Oleksandr Natalenko
2022-01-11 18:16 ` PATCH v4 ASUS EC Sensors Barnabás Pőcze
2022-01-11 18:34   ` Eugene Shalygin
2022-01-16 19:28 ` Oleksandr Natalenko [this message]
2022-01-16 19:47   ` Eugene Shalygin
  -- strict thread matches above, loose matches on Subject: below --
2022-01-11 16:56 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=2613330.mvXUDI8C0e@natalenko.name \
    --to=oleksandr@natalenko.name \
    --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=linux@roeck-us.net \
    --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