From: Suniel Mahesh <sunil@amarulasolutions.com>
To: Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michael Trimarchi <michael@amarulasolutions.com>,
Jagan Teki <jagan@amarulasolutions.com>
Cc: linux-kernel@vger.kernel.org, linux-amarula@amarulasolutions.com,
USB list <linux-usb@vger.kernel.org>
Subject: [RFC 0/2] Extend functionality for GET_REPORT
Date: Mon, 1 Aug 2022 18:00:08 +0530 [thread overview]
Message-ID: <20220801123010.2984864-1-sunil@amarulasolutions.com> (raw)
This series does the following:
patch 1/2 extends functionality for GET_REPORT.
The current kernel implementation for GET_REPORT is that the kernel
sends back a zero filled report (of length == report_length), when
the Host request's a particular report from the device/gadget.
This changeset extends functionality for GET_REPORT by sending a
particular report based on report type and report number.
patch 2/2 adds a test application to test the extended
functionality.
please review and share your thoughts.
Suniel Mahesh (2):
usb: gadget: f_hid: Extend functionality for GET_REPORT mode
HID: ghid: add example program for GET_REPORT
drivers/usb/gadget/function/f_hid.c | 166 ++++++++++++++++++++++++++-
include/{ => uapi}/linux/usb/g_hid.h | 10 ++
samples/Kconfig | 10 ++
samples/Makefile | 1 +
samples/ghid/Makefile | 4 +
samples/ghid/test-hid.c | 134 +++++++++++++++++++++
6 files changed, 323 insertions(+), 2 deletions(-)
rename include/{ => uapi}/linux/usb/g_hid.h (72%)
create mode 100644 samples/ghid/Makefile
create mode 100644 samples/ghid/test-hid.c
--
2.25.1
next reply other threads:[~2022-08-01 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 12:30 Suniel Mahesh [this message]
2022-08-01 12:30 ` [RFC 1/2] usb: gadget: f_hid: Extend functionality for GET_REPORT mode Suniel Mahesh
2022-08-01 12:30 ` [RFC 2/2] HID: ghid: add example program for GET_REPORT Suniel Mahesh
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=20220801123010.2984864-1-sunil@amarulasolutions.com \
--to=sunil@amarulasolutions.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jagan@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael@amarulasolutions.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®