From: Guenter Roeck <linux@roeck-us.net>
To: linux-hwmon@vger.kernel.org
Cc: Tomasz Bojanowski <tomasz@bojanowski.me>,
Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH 0/4] hwmon: (msi_mystic_light) Add support for additional MSI motherboards
Date: Sat, 7 Nov 2026 16:01:27 -0800 [thread overview]
Message-ID: <20261108000131.1249664-1-linux@roeck-us.net> (raw)
This series extends the msi_mystic_light hwmon driver to support voltage
monitoring on three MSI 500- and 600-series motherboards:
- MSI MAG B550M MORTAR MAX WIFI (MS-7C94, USB ID 1462:7c94)
- MSI MAG B650 TOMAHAWK WIFI (MS-7D75, USB ID 1462:7d75)
- MSI MAG B650M MORTAR WIFI (MS-7D76, USB ID 1462:7d76)
Unlike the 800-series MS-7E61 motherboard initially supported by the
driver, which exposes voltage readings synchronously via a
HID_REQ_GET_REPORT request on feature report 0xf0, the Mystic Light
controllers on these 500- and 600-series boards require sending an
output report to request sensor data and subsequently deliver the sensor
readings asynchronously via a HID raw event.
Patch 1 rearranges structures and per-board definitions so board-specific
read callbacks can be added without forward declarations.
Patch 2 drops redundant hid_hw_power() calls around sensor report reads,
since the HID device is already kept open for the lifetime of the driver
binding.
Patch 3 introduces a per-board read_report() callback in struct
msi_ml_board.
Patch 4 adds the output-report/raw-event read implementation, board
definitions, DMI/USB ID entries, and documentation for MS-7C94, MS-7D75,
and MS-7D76.
Guenter Roeck (4):
hwmon: (msi_mystic_light) Rearrange code to simplify adding per-board
read functions
hwmon: (msi_mystic_light) Stop calling hid_hw_power()
hwmon: (msi_mystic_light) Make sensor read function board specific
hwmon: (msi_mystic_light) Add support for additional boards
Documentation/hwmon/msi_mystic_light.rst | 59 +++++-
drivers/hwmon/msi_mystic_light.c | 222 ++++++++++++++++++-----
2 files changed, 227 insertions(+), 54 deletions(-)
--
2.56.0
next reply other threads:[~2026-11-08 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 0:01 Guenter Roeck [this message]
2026-11-08 0:01 ` [PATCH 1/4] hwmon: (msi_mystic_light) Rearrange code to simplify adding per-board read functions Guenter Roeck
2026-11-08 0:01 ` [PATCH 2/4] hwmon: (msi_mystic_light) Stop calling hid_hw_power() Guenter Roeck
2026-11-08 0:01 ` [PATCH 3/4] hwmon: (msi_mystic_light) Make sensor read function board specific Guenter Roeck
2026-11-08 0:01 ` [PATCH 4/4] hwmon: (msi_mystic_light) Add support for additional boards Guenter Roeck
2026-11-08 8:14 ` [PATCH 0/4] hwmon: (msi_mystic_light) Add support for additional MSI motherboards Tomasz Bojanowski
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=20261108000131.1249664-1-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=tomasz@bojanowski.me \
/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