linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Staffan Melin <staffan.melin@oscillator.se>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: zhangheng <zhangheng@kylinos.cn>,
	1114557@bugs.debian.org,
	Linux Hid <linuxhid@cosmicgizmosystems.com>,
	jikos@kernel.org, bentiss@kernel.org,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Bug#1114557: [PATCH v2] HID: quirks: Add device descriptor for 4c4a:4155
Date: Thu, 23 Oct 2025 15:10:08 +0200	[thread overview]
Message-ID: <638f3938581848a8ca0a6dcb981dfbdd@oscillator.se> (raw)
In-Reply-To: <aPhz5L-ECc8CzA0a@eldamar.lan>

Thank you Salvatore, for moving this forward.

I can add that the issue has been reported by several users on a GPD DUO 
channel on Discord -- all are on newer kernels but have different Linux 
distributions.

I can also confirm that the patch does solve my problem. Looking forward 
to some resolution of this, as it stops me from upgrading to Testing. :)

Best regards,

Staffan


On 2025-10-22 08:04, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Mon, Oct 13, 2025 at 04:32:39PM +0800, zhangheng wrote:
>> It happened to be the holiday, so communication was a bit troublesome.
>> 
>> However, after a brief discussion with the microphone manufacturer,
>> 
>> it was found that the serial number was still 20201111000001 on 
>> another
>> 
>> microphone device. So, should we add it?
> 
> As this issue still affects one of our users in Debian, is there
> anything which can be done to unblock the situation? Does that mean
> that the proposed patch is not good for the microphone device?
> 
> My understanding is that it fixes at least Staffan's case which
> regressed from 1a8953f4f774 ("HID: Add IGNORE quirk for
> SMARTLINKTECHNOLOGY").
> 
> Regards,
> Salvatore

  reply	other threads:[~2025-10-23 13:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23  2:24 [PATCH v2] HID: quirks: Add device descriptor for 4c4a:4155 Zhang Heng
2025-09-29  0:42 ` Linux Hid
2025-10-13  8:32   ` zhangheng
2025-10-22  6:04     ` Bug#1114557: " Salvatore Bonaccorso
2025-10-23 13:10       ` Staffan Melin [this message]
2025-10-24  0:39     ` Terry Junge
2025-10-24  3:32       ` zhangheng
2025-10-24 14:22         ` Staffan Melin
2025-10-24 22:28         ` Terry Junge
2025-10-26  3:34           ` [PATCH v4] HID: quirks: Change manufacturer " zhangheng
2025-10-26 10:45             ` Staffan Melin
2025-10-26 19:58             ` Terry Junge
2025-10-30 10:24             ` Jiri Kosina

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=638f3938581848a8ca0a6dcb981dfbdd@oscillator.se \
    --to=staffan.melin@oscillator.se \
    --cc=1114557@bugs.debian.org \
    --cc=bentiss@kernel.org \
    --cc=carnil@debian.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxhid@cosmicgizmosystems.com \
    --cc=zhangheng@kylinos.cn \
    /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;
as well as URLs for NNTP newsgroup(s).