From: Maxim Devaev <mdevaev@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: balbi@kernel.org, gregkh@linuxfoundation.org,
ruslan.bilovol@gmail.com, mika.westerberg@linux.intel.com,
maze@google.com, jj251510319013@gmail.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: f_hid: optional SETUP/SET_REPORT mode
Date: Fri, 13 Aug 2021 23:40:22 +0300 [thread overview]
Message-ID: <20210813234022.5d5644ae@reki> (raw)
In-Reply-To: <20210813232212.5cba6d33@reki>
В Fri, 13 Aug 2021 23:22:12 +0300
Maxim Devaev <mdevaev@gmail.com> пишет:
> Alan Stern <stern@rowland.harvard.edu> wrote:
> > In other words, a device does not need to have an interrupt-OUT
> > endpoint, but if it does have one then the host must use it.
>
> You're right. Although the actual behavior of the hosts is not different
> from what I wrote - they really just ignore out endpoint.
> I will eventually fix this in the patch description.
It seems that I have confused everything even more, sorry. I will explain.
There are three possible host behaviors:
(1) The host works with the OUT endpoint as it describes the standard
and transmits reports through it.
(2) The host works with IN endpoint, but refuses to transmit reports
via OUT endpoint at all. In the case of the keyboard, it will work,
but it will not receive the status of the LEDs.
(3) The host sees OUT endpoint and either refuses to use such a device at all,
or goes crazy in various ways.
In both cases (2) and (3), using SETUP/SET_REPORT solves the problem.
Therefore, I offer this as an option to solve compatibility problems.
Yes, in fact, this is not our problem, but it is impossible to fix the drivers
of all these proprietary devices. Moreover, I have never met a keyboard
with OUT endpoint, absolutely all of them use SETUP/SET_REPORT.
next prev parent reply other threads:[~2021-08-13 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 11:45 [PATCH] usb: gadget: f_hid: optional SETUP/SET_REPORT mode Maxim Devaev
2021-08-13 14:58 ` Alan Stern
2021-08-13 20:22 ` Maxim Devaev
2021-08-13 20:40 ` Maxim Devaev [this message]
2021-08-14 1:45 ` Alan Stern
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=20210813234022.5d5644ae@reki \
--to=mdevaev@gmail.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jj251510319013@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maze@google.com \
--cc=mika.westerberg@linux.intel.com \
--cc=ruslan.bilovol@gmail.com \
--cc=stern@rowland.harvard.edu \
/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