From: Guenter Roeck <linux@roeck-us.net>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: remy@demangeot.net, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] hwmon: (asus-ec-sensors) add water temperatures for MAXIMUS IX EXTREME
Date: Tue, 27 Oct 2026 09:21:04 -0700 [thread overview]
Message-ID: <1fcc110e-7269-44de-a415-1848922f75f6@roeck-us.net> (raw)
In-Reply-To: <CAB95QAQaogxV6KO5kpv9RBpzhhmH_N3Dvvy=nqWHOG6qAQB_aw@mail.gmail.com>
On Tue, Oct 27, 2026 at 10:23:33AM +0100, Eugene Shalygin wrote:
> Hi,
>
> On Mon, 26 Oct 2026 at 09:57, Remy Demangeot via B4 Relay
> <devnull+remy.demangeot.net@kernel.org> wrote:
> >
> > From: Remy Demangeot <remy@demangeot.net>
> >
> > The MAXIMUS IX EXTREME has a second EC (firmware ID "RGE2-Z270-0109"),
> > not handled by the ACPI EC driver, at I/O ports 0x68 (data) and 0x6c
> > (command/status). It uses the standard EC protocol (0x80 read, 0x81
> > write) and the same bank register (0xff).
>
> I'm not fond of re-implementing EC access logic in this driver. I
> believe the ec.c driver needs to be changed to allow us to simply
> create another acpi_ec structure to operate the second EC.
>
Me not either, but that would (should ?) be a separate effort and might
take a substantial amount of time to get accepted upstream.
Guenter
next prev parent reply other threads:[~2026-10-27 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 8:57 [PATCH 0/3] hwmon: (asus-ec-sensors) more MAXIMUS IX EXTREME sensors Remy Demangeot via B4 Relay
2026-10-26 8:57 ` [PATCH 1/3] hwmon: (asus-ec-sensors) add EXT_Sensor temperatures for MAXIMUS IX EXTREME Remy Demangeot via B4 Relay
2026-10-26 19:33 ` Guenter Roeck
2026-10-26 8:57 ` [PATCH 2/3] hwmon: (asus-ec-sensors) add fan extension card fans " Remy Demangeot via B4 Relay
2026-10-26 19:33 ` Guenter Roeck
2026-10-26 8:57 ` [PATCH 3/3] hwmon: (asus-ec-sensors) add water temperatures " Remy Demangeot via B4 Relay
2026-10-26 19:34 ` Guenter Roeck
2026-10-27 9:23 ` Eugene Shalygin
2026-10-27 16:21 ` Guenter Roeck [this message]
2026-10-28 9:57 ` Eugene Shalygin
2026-10-28 20:55 ` Armin Wolf
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=1fcc110e-7269-44de-a415-1848922f75f6@roeck-us.net \
--to=linux@roeck-us.net \
--cc=eugene.shalygin@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=remy@demangeot.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
all inboxes | Powered by JetHome®