From: Denis Pauk <pauk.denis@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: eugene.shalygin@gmail.com, andy.shevchenko@gmail.com,
pauk.denis@gmail.com, platform-driver-x86@vger.kernel.org,
thomas@weissschuh.net, Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] hwmon: (nct6775) Support lock by ACPI mutex
Date: Mon, 22 Nov 2021 23:28:47 +0200 [thread overview]
Message-ID: <20211122212850.321542-1-pauk.denis@gmail.com> (raw)
Lock by ACPI mutex that is required for support ASUS MAXIMUS VII HERO
motherboard. In other case, all methods are returned zero instead of real
values. Code uses acpi mutex before any IO operations in case when such
acpi mutex is known.
Patch series adds additional check for ChipID, and if method returned
zero, all calls by acpi_wmi are disabled.
Could you please review? Is it correct usage of ACPI mutex or better
to use some other method for reuse same ACPI mutex?
---
Denis Pauk (3):
hwmon: (nct6775) Use nct6775_*() lock function pointers in
nct6775_data.
hwmon: (nct6775) Implement custom lock by ACPI mutex.
hwmon: (nct6775) add MAXIMUS VII HERO.
drivers/hwmon/nct6775.c | 358 +++++++++++++++++++++++++++++-----------
1 file changed, 259 insertions(+), 99 deletions(-)
base-commit: fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf
--
2.33.0
next reply other threads:[~2021-11-22 21:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 21:28 Denis Pauk [this message]
2021-11-22 21:28 ` [PATCH 1/3] hwmon: (nct6775) Use nct6775_*() lock function pointers in nct6775_data Denis Pauk
2021-11-24 16:03 ` Andy Shevchenko
2021-11-25 21:07 ` Denis Pauk
2021-11-25 21:50 ` Andy Shevchenko
2021-11-22 21:28 ` [PATCH 2/3] hwmon: (nct6775) Implement custom lock by ACPI mutex Denis Pauk
2021-11-24 16:10 ` Andy Shevchenko
2021-11-25 13:14 ` Eugene Shalygin
2021-11-25 13:16 ` Eugene Shalygin
2021-11-25 13:51 ` Guenter Roeck
2021-11-25 13:54 ` Eugene Shalygin
2021-11-25 13:51 ` Andy Shevchenko
2021-11-25 14:00 ` Eugene Shalygin
2021-11-25 19:54 ` Guenter Roeck
2021-11-25 20:05 ` Eugene Shalygin
2021-11-25 20:09 ` Andy Shevchenko
2021-11-25 20:25 ` Denis Pauk
2021-11-25 20:33 ` Eugene Shalygin
2021-11-25 21:52 ` Andy Shevchenko
2021-11-25 20:28 ` Eugene Shalygin
2021-11-22 21:28 ` [PATCH 3/3] hwmon: (nct6775) add MAXIMUS VII HERO Denis Pauk
2021-11-24 16:21 ` Andy Shevchenko
2021-11-24 16:24 ` Andy Shevchenko
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=20211122212850.321542-1-pauk.denis@gmail.com \
--to=pauk.denis@gmail.com \
--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=platform-driver-x86@vger.kernel.org \
--cc=thomas@weissschuh.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;
as well as URLs for NNTP newsgroup(s).