mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bozhen Peng <bozhenpeng93@gmail.com>
To: Anton Karasev <uselessfire@gmail.com>
Cc: Hans de Goede <hansg@kernel.org>,
	Ilpo Jarvinen <ilpo.jarvinen@linux.intel.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, W_Armin@gmx.de,
	qby140326@gmail.com, ilya.gladyshev@linux.dev, chris@miget.com,
	kento@kekto.ru, wolf109909@outlook.com, vlku.milos.fun@gmail.com,
	btx342@gmail.com, zsanya322@gmail.com, i@rsplwe.com,
	martiya.ar@gmail.com, nika@nikableh.moe
Subject: Re: [PATCH] platform/x86: bitland-mifs-wmi: Only expose kb_mode when it is supported
Date: Sat, 17 Oct 2026 20:03:00 -0700	[thread overview]
Message-ID: <b2b8aeee-08a5-479b-bac4-a38ac606a037@gmail.com> (raw)
In-Reply-To: <20261008-bitland-kb-mode-v1-uselessfire@gmail.com>

Hi Anton,

I tested your patch as posted on my MECHREVO WUJIE15 PRO
(WUJIE15 Series-HPT), using your stated for-next base: 

98f039265e580291d5e76a11b2072541fbb1c393

I booted the baseline and then the same kernel with only your patch
applied. On the baseline, kb_mode was present, but reading it returned
"Input/output error". With your patch, kb_mode was absent and I got:

  kb_mode not supported (-5), hiding it

The GET produces an ACPI AE_NOT_FOUND for HEC.LEDM on this machine.
With your patch, the probe still reports the ACPI error, 
but kb_mode is correctly hidden.

I cycled the keyboard backlight with Fn+F7 from off through levels
1, 2 and 3, then back to off. All levels worked. During this check,
atkbd logged unknown scancode 0xf6 messages.

This confirms the unsupported-kb_mode case on HPT. My keyboard backlight
is not RGB, so I didn't tested the supported RGB-mode case.

Tested-by: Bozhen Peng <bozhenpeng93@gmail.com>

Thanks,
Bozhen

      reply	other threads:[~2026-10-18  3:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 15:25 Anton Karasev
2026-10-18  3:03 ` Bozhen Peng [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=b2b8aeee-08a5-479b-bac4-a38ac606a037@gmail.com \
    --to=bozhenpeng93@gmail.com \
    --cc=W_Armin@gmx.de \
    --cc=btx342@gmail.com \
    --cc=chris@miget.com \
    --cc=hansg@kernel.org \
    --cc=i@rsplwe.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=ilya.gladyshev@linux.dev \
    --cc=kento@kekto.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martiya.ar@gmail.com \
    --cc=nika@nikableh.moe \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=qby140326@gmail.com \
    --cc=uselessfire@gmail.com \
    --cc=vlku.milos.fun@gmail.com \
    --cc=wolf109909@outlook.com \
    --cc=zsanya322@gmail.com \
    /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®