From: Mario Limonciello <mario.limonciello@amd.com>
To: Jonathan Grant <jg@jguk.org>,
platform-driver-x86@vger.kernel.org, luke@ljones.dev
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: asus-wmi: log thermal notification event
Date: Mon, 16 Mar 2026 10:24:14 -0500 [thread overview]
Message-ID: <7f2f4b15-2fad-4784-a524-7f92f6b21a94@amd.com> (raw)
In-Reply-To: <94dbe1e1-d706-47aa-abf5-f5d76aacf017@jguk.org>
On 3/16/26 07:49, Jonathan Grant wrote:
> [You don't often get email from jg@jguk.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> From e110b7489b320588a7d334bf0a4e20e3e25784e7 Mon Sep 17 00:00:00 2001
> From: Jonathan Grant <jg@jguk.org>
> Date: Sat, 14 Mar 2026 02:11:09 +0000
> Subject: [PATCH] platform/x86: asus-wmi: log thermal notification event
>
> Print a diagnostic message when the ASUS WMI interface receives
> event 0x6d. This event was observed shortly before thermal
> shutdown on an ASUS N56VB under heavy system load. The message
> helps diagnose unexpected thermal power-offs.
>
> Signed-off-by: Jonathan Grant <jg@jguk.org>
> ---
> v2:
> - follow kernel patch guidelines
> - rename event to NOTIFY_THERMAL
> - document that event 0x6d was observed before thermal shutdown
> on ASUS N56VB (BIOS WMI version 7.9, SFUN value 0x6a0877)
> - improve commit message description
> - remove stray blank line
>
> drivers/platform/x86/asus-wmi.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/asus-wmi.c b/drivers/platform/x86/asus-wmi.c
> index 7c0915e097ba..6ab3886ad28f 100644
> --- a/drivers/platform/x86/asus-wmi.c
> +++ b/drivers/platform/x86/asus-wmi.c
> @@ -70,6 +70,7 @@ module_param(fnlock_default, bool, 0444);
> #define NOTIFY_KBD_TTP 0xae
> #define NOTIFY_LID_FLIP 0xfa
> #define NOTIFY_LID_FLIP_ROG 0xbd
> +#define NOTIFY_THERMAL 0x6d
>
> #define ASUS_WMI_FNLOCK_BIOS_DISABLED BIT(0)
>
> @@ -4590,7 +4591,6 @@ static void asus_wmi_handle_event_code(int code, struct asus_wmi *asus)
> if (asus->throttle_thermal_policy_dev)
> platform_profile_cycle();
> return;
> -
You shouldn't change unrelated whitespace
> }
>
> if (is_display_toggle(code) && asus->driver->quirks->no_display_toggle)
> @@ -4598,7 +4598,10 @@ static void asus_wmi_handle_event_code(int code, struct asus_wmi *asus)
>
> if (!sparse_keymap_report_event(asus->inputdev, code,
> key_value, autorelease))
> - pr_info("Unknown key code 0x%x\n", code);
> + if (code == NOTIFY_THERMAL)
> + pr_info("Thermal state change\n");
> + else
> + pr_info("Unknown key code 0x%x\n", code);
> }
>
> static void asus_wmi_notify(union acpi_object *obj, void *context)
> --
> 2.43.0
next prev parent reply other threads:[~2026-03-16 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56532bb3-c604-484e-9716-edda3758f627@jguk.org>
[not found] ` <50cc3d4b-5e5a-422c-9abd-556488710988@amd.com>
2026-03-16 12:49 ` Jonathan Grant
2026-03-16 15:24 ` Mario Limonciello [this message]
2026-03-17 21:30 ` [PATCH v3] " Jonathan Grant
2026-03-18 1:40 ` Mario Limonciello
2026-03-17 0:53 ` [PATCH v2] " kernel test robot
2026-03-17 17:33 ` kernel test robot
2026-03-17 20:30 ` kernel test robot
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=7f2f4b15-2fad-4784-a524-7f92f6b21a94@amd.com \
--to=mario.limonciello@amd.com \
--cc=jg@jguk.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@vger.kernel.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®