From: Eugene Shalygin <eugene.shalygin@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Eugene Shalygin <eugene.shalygin@gmail.com>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] asus-ec-sensors: add support for board families
Date: Tue, 26 Apr 2022 11:23:36 +0200 [thread overview]
Message-ID: <20220426092340.495704-1-eugene.shalygin@gmail.com> (raw)
Users provided information for boards from AMD-400 and sTRX40 families
and demonstrated that sensor addresses differ from those for the AMD-500
family. Also the AMD-400 family board uses the global ACPI lock instead
of a dedicated mutex to guard access to the hardware.
This patchset implements required changes to support other board
families:
- per-family sensor definitions
- options to choose hardware/state guard mutex: an AML mutex or the
global ACPI lock.
These changes are used to add support for the PRIME X470-PRO board.
Changes in v2:
- Removed the case without ACPI mutex where the state was guarded using
the normal mutex. After receiving an update from user that case
turned out to be non-existent.
- Removed the __initconst attribute from the board data array.
- Updated documentation to include the special string for the mutex
path module parameters which make the driver use the global ACPI
lock.
Eugene Shalygin (4):
hwmon: (asus-ec-sensors) introduce ec_board_info struct for board data
hwmon: (asus-ec-sensors) implement locking via the ACPI global lock
hwmon: (asus-ec-sensors) add support for board families
hwmon: (asus-ec-sensors) add PRIME X470-PRO board
Documentation/hwmon/asus_ec_sensors.rst | 2 +
drivers/hwmon/asus-ec-sensors.c | 412 +++++++++++++++++-------
2 files changed, 294 insertions(+), 120 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-26 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 9:23 Eugene Shalygin [this message]
2022-04-26 9:23 ` [PATCH v2 1/4] hwmon: (asus-ec-sensors) introduce ec_board_info struct for board data Eugene Shalygin
2022-04-26 15:16 ` Guenter Roeck
2022-04-27 9:32 ` Eugene Shalygin
2022-04-27 12:04 ` Guenter Roeck
2022-04-27 12:16 ` Eugene Shalygin
2022-04-27 13:20 ` Guenter Roeck
2022-04-27 13:34 ` Eugene Shalygin
2022-04-27 13:41 ` Guenter Roeck
2022-04-27 13:46 ` Eugene Shalygin
2022-04-26 9:23 ` [PATCH v2 2/4] hwmon: (asus-ec-sensors) implement locking via the ACPI global lock Eugene Shalygin
2022-04-26 9:23 ` [PATCH v2 3/4] hwmon: (asus-ec-sensors) add support for board families Eugene Shalygin
2022-04-26 15:24 ` Guenter Roeck
2022-04-26 21:50 ` Eugene Shalygin
2022-04-26 9:23 ` [PATCH v2 4/4] hwmon: (asus-ec-sensors) add PRIME X470-PRO board 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=20220426092340.495704-1-eugene.shalygin@gmail.com \
--to=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 \
/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