mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Remy Demangeot <remy@demangeot.net>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Eugene Shalygin <eugene.shalygin@gmail.com>,
	linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (asus-ec-sensors) add MAXIMUS IX EXTREME
Date: Sun, 25 Oct 2026 17:32:10 -0700	[thread overview]
Message-ID: <bd8640cb-cc7c-4e52-afe6-635c0dce0ab6@roeck-us.net> (raw)
In-Reply-To: <20261015-b4-m9e-extreme-v1-1-621da921e320@demangeot.net>

On Thu, Oct 15, 2026 at 06:09:31PM +0200, Remy Demangeot wrote:
> From: Remy Demangeot <remy@demangeot.net>
> 
> Add support for the ROG MAXIMUS IX EXTREME (Intel Z270). The board
> uses the same EC layout as the PRIME Z270-A for the chipset and
> T_Sensor temperatures, and additionally exposes the VRM temperature
> at the same register as the 300-series boards (bank 0, 0x3e), so add
> that sensor to the Intel 200-series family.
> 
> The hardware access mutex is \_SB_.PCI0.LPCB.SIO1.MUT0, as on the
> PRIME Z270-A (verified in the board's DSDT).
> 
> Readings were checked against HWiNFO 8.54 on the same machine
> (Chipset 47 C, T_Sensor 25 C, VRM 32 C).
> 
> Signed-off-by: Remy Demangeot <remy@demangeot.net>

Applied.

> ---
> The board's EC also exposes more sensors that HWiNFO reads, but they
> need access patterns the driver does not have yet:
>  - three extension card fans (EXT_FAN1-3): write 0x0a/0x0b/0x0c to
>    bank 0 register 0x43 (selector), then read 0x57:0x58 (BE RPM);
>  - EXT_Sensor1-3 temperatures at bank 0, 0x60-0x62;
>  - Water_In/Out and Water_In2/Out2 on a second EC (firmware ID
>    "RGE2-Z270-0109") at I/O ports 0x68/0x6c, bank 1, registers
>    0x0d/0x0b/0x13/0x11 (same offsets as Water_In/Out on AMD boards).
> 
> I have a working out-of-tree driver for these and can prepare follow-up
> patches if this approach would be acceptable.

I am curions - any reason to assume that it would _not_ be acceptable ?

Thanks,
Guenter

      reply	other threads:[~2026-10-26  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 16:09 Remy Demangeot via B4 Relay
2026-10-26  0:32 ` Guenter Roeck [this message]

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=bd8640cb-cc7c-4e52-afe6-635c0dce0ab6@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=corbet@lwn.net \
    --cc=eugene.shalygin@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=remy@demangeot.net \
    --cc=skhan@linuxfoundation.org \
    /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®