The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Cryolitia PukNgae <cryolitia.pukngae@linux.dev>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@kernel.org, zhanjun@uniontech.com,
	niecheng1@uniontech.com, cryolitia@uniontech.com,
	Mingcong Bai <jeffbai@aosc.io>,
	Kexy Biscuit <kexybiscuit@aosc.io>,
	Mikura Kyouka <mikurakyouka@aosc.io>,
	"foad.elkhattabi" <foad.elkhattabi@gmail.com>
Subject: Re: [PATCH] Input: atkbd - skip deactivate for HONOR FMB-P's internal keyboard
Date: Wed, 22 Oct 2025 13:20:01 +0200	[thread overview]
Message-ID: <dde1e6eb-34e2-4d71-99b3-c5d8fad4940c@kernel.org> (raw)
In-Reply-To: <20251022-honor-v1-1-ff894ed271a9@linux.dev>

Hi,

On 22-Oct-25 12:40 PM, Cryolitia PukNgae wrote:
> After commit 9cf6e24c9fbf17e52de9fff07f12be7565ea6d61 ("Input: atkbd -
> do not skip atkbd_deactivate() when skipping ATKBD_CMD_GETID"), HONOR
> FMB-P, aka HONOR MagicBook Pro 14 2025's internal keyboard stops
> working. Adding the atkbd_deactivate_fixup quirk fixes it.
> 
> DMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025
> 
> Fixes: 9cf6e24c9fbf17e52de9fff07f12be7565ea6d61 ("Input: atkbd - do not skip atkbd_deactivate() when skipping ATKBD_CMD_GETID")
> Reported-by: Mikura Kyouka <mikurakyouka@aosc.io>
> Link: https://www.xiaohongshu.com/explore/68738d0a0000000012015a79
> Link: https://club.honor.com/cn/thread-29463529-1-1.html
> Link: https://club.honor.com/cn/thread-29490444-1-1.html
> Reported-by: foad.elkhattabi <foad.elkhattabi@gmail.com>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=220384
> Signed-off-by: Cryolitia PukNgae <cryolitia.pukngae@linux.dev>

Thanks, patch looks good to me:

Reviewed-by: Hans de Goede <hansg@kernel.org>

Regards,

Hans



> ---
>  drivers/input/keyboard/atkbd.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
> index 6c999d89ee4b..422e28ad1e8e 100644
> --- a/drivers/input/keyboard/atkbd.c
> +++ b/drivers/input/keyboard/atkbd.c
> @@ -1937,6 +1937,13 @@ static const struct dmi_system_id atkbd_dmi_quirk_table[] __initconst = {
>  		},
>  		.callback = atkbd_deactivate_fixup,
>  	},
> +	{
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "HONOR"),
> +			DMI_MATCH(DMI_PRODUCT_NAME, "FMB-P"),
> +		},
> +		.callback = atkbd_deactivate_fixup,
> +	},
>  	{ }
>  };
>  
> 
> ---
> base-commit: 552c50713f273b494ac6c77052032a49bc9255e2
> change-id: 20251022-honor-8bc9bef8eba7
> 
> Best regards,


      reply	other threads:[~2025-10-22 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 10:40 [PATCH] Input: atkbd - skip deactivate for HONOR FMB-P's internal keyboard Cryolitia PukNgae
2025-10-22 11:20 ` Hans de Goede [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=dde1e6eb-34e2-4d71-99b3-c5d8fad4940c@kernel.org \
    --to=hansg@kernel.org \
    --cc=cryolitia.pukngae@linux.dev \
    --cc=cryolitia@uniontech.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=foad.elkhattabi@gmail.com \
    --cc=jeffbai@aosc.io \
    --cc=kexybiscuit@aosc.io \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikurakyouka@aosc.io \
    --cc=niecheng1@uniontech.com \
    --cc=stable@kernel.org \
    --cc=zhanjun@uniontech.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