linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Terry Junge <linuxhid@cosmicgizmosystems.com>
To: zhangheng <zhangheng@kylinos.cn>,
	jikos@kernel.org, bentiss@kernel.org,
	staffan.melin@oscillator.se
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	1114557@bugs.debian.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] HID: quirks: Add device descriptor for 4c4a:4155
Date: Fri, 24 Oct 2025 15:28:53 -0700	[thread overview]
Message-ID: <c7aab08b-52fa-41ef-a7fb-118298bb93aa@cosmicgizmosystems.com> (raw)
In-Reply-To: <8f0155d4-72a7-45ec-a272-7892e783bbed@kylinos.cn>

Hi Zhang,

Since the manufacturer has verified that all the microphones have the 
same serial number you could add the test for that as well if you want.

The report descriptor is clearly for a keyboard/keypad and should be 
ignored.

In any case, the current v3 attached patch does resolve the conflict.

Reviewed-by: Terry Junge <linuxhid@cosmicgizmosystems.com>

On 10/23/2025 8:32 PM, zhangheng wrote:
> Hi Terry Junge，
> 
> I have made the changes as per your suggestion.
> mic.txt is the microphone report descriptor and is working properly.
> 
> 
> 

  parent reply	other threads:[~2025-10-24 22:28 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
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 [this message]
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=c7aab08b-52fa-41ef-a7fb-118298bb93aa@cosmicgizmosystems.com \
    --to=linuxhid@cosmicgizmosystems.com \
    --cc=1114557@bugs.debian.org \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=staffan.melin@oscillator.se \
    --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).