From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: linux-input@vger.kernel.org
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
David Rheinsberg <david.rheinsberg@gmail.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: [RFC PATCH 0/2] Handling of non-numbered feature reports by hidraw
Date: Mon, 5 Dec 2022 13:03:52 -0800 [thread overview]
Message-ID: <20221205210354.11846-1-andrew.smirnov@gmail.com> (raw)
Hi everyone,
I'm working on a firmware of a device that exposes a HID interface via
USB and/or BLE and uses, among other things, non-numbered feature
reports. Included in this series are two paches I had to create in
order for hidraw devices created for aforementioned subsystems to
behave in the same way when exerciesd by the same test tool.
I don't know if the patches are acceptable as-is WRT to not breaking
existing userspace, hence the RFC tag.
Andrey Smirnov (2):
HID: uhid: Don't send the report ID if it's zero
HID: usbhid: Don't include report ID zero into returned data
drivers/hid/uhid.c | 15 ++++++++++++---
drivers/hid/usbhid/hid-core.c | 14 --------------
2 files changed, 12 insertions(+), 17 deletions(-)
--
2.34.1
next reply other threads:[~2022-12-05 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 21:03 Andrey Smirnov [this message]
2022-12-05 21:03 ` [RFC PATCH 1/2] HID: uhid: Don't send the report ID if it's zero Andrey Smirnov
2022-12-12 15:23 ` David Rheinsberg
2022-12-15 20:44 ` Andrey Smirnov
2022-12-05 21:03 ` [RFC PATCH 2/2] HID: usbhid: Don't include report ID zero into returned data Andrey Smirnov
2022-12-08 15:46 ` [RFC PATCH 0/2] Handling of non-numbered feature reports by hidraw David Rheinsberg
2022-12-08 20:58 ` Andrey Smirnov
2022-12-12 15:24 ` David Rheinsberg
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=20221205210354.11846-1-andrew.smirnov@gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=david.rheinsberg@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).