On Tue, Mar 03, 2026 at 06:12:53AM +0000, Jingyuan Liang wrote: > From: Jarrett Schultz <[email protected]> > > Originally output_report callback was described as must-be asynchronous, > but that is not the case in some implementations, namely i2c-hid. > Correct the documentation to say that it may be asynchronous. > > Signed-off-by: Dmitry Antipov <[email protected]> > Signed-off-by: Jingyuan Liang <[email protected]> > --- > Documentation/hid/hid-transport.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/hid/hid-transport.rst > b/Documentation/hid/hid-transport.rst > index 6f1692da296c..2008cf432af1 100644 > --- a/Documentation/hid/hid-transport.rst > +++ b/Documentation/hid/hid-transport.rst > @@ -327,8 +327,8 @@ The available HID callbacks are: > > Send raw output report via intr channel. Used by some HID device drivers > which require high throughput for outgoing requests on the intr channel. > This > - must not cause SET_REPORT calls! This must be implemented as asynchronous > - output report on the intr channel! > + must not cause SET_REPORT calls! This call might be asynchronous, so the > + caller should not expect an immediate response!
Reviewed-by: Dmitry Torokhov <[email protected]> Thanks. -- Dmitry
