From: Eugene Shalygin <eugene.shalygin@gmail.com>
To: eugene.shalygin@gmail.com
Cc: darcagn@protonmail.com, Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] asus-ec-sensors: add support for board families
Date: Sun, 27 Mar 2022 14:14:00 +0200 [thread overview]
Message-ID: <20220327121404.1702631-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, the
global ACPI lock, and a regular mutex in case no ACPI lock required.
These changes are used to add support for the PRIME X470-PRO board.
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
drivers/hwmon/asus-ec-sensors.c | 431 +++++++++++++++++++++++---------
1 file changed, 310 insertions(+), 121 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-27 12:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 12:14 Eugene Shalygin [this message]
2022-03-27 12:14 ` [PATCH 1/4] hwmon: (asus-ec-sensors) introduce ec_board_info struct for board data Eugene Shalygin
2022-03-29 13:44 ` Guenter Roeck
2022-03-29 19:22 ` Eugene Shalygin
2022-03-29 20:26 ` Guenter Roeck
2022-03-30 7:51 ` Eugene Shalygin
2022-03-30 14:09 ` Guenter Roeck
2022-03-27 12:14 ` [PATCH 2/4] hwmon: (asus-ec-sensors) implement locking via the ACPI global lock Eugene Shalygin
2022-03-27 16:21 ` Eugene Shalygin
2022-03-27 18:04 ` Guenter Roeck
2022-03-27 18:51 ` Eugene Shalygin
2022-03-27 23:25 ` Guenter Roeck
2022-03-28 14:44 ` Eugene Shalygin
2022-03-28 15:50 ` Nathan Chancellor
2022-03-29 11:36 ` Eugene Shalygin
2022-03-29 21:23 ` Guenter Roeck
2022-03-29 22:11 ` Eugene Shalygin
2022-03-29 23:37 ` Guenter Roeck
2022-03-30 7:36 ` Eugene Shalygin
2022-03-27 12:14 ` [PATCH 3/4] hwmon: (asus-ec-sensors) add support for board families Eugene Shalygin
2022-03-27 12:14 ` [PATCH 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=20220327121404.1702631-1-eugene.shalygin@gmail.com \
--to=eugene.shalygin@gmail.com \
--cc=darcagn@protonmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.