From: Guenter Roeck <linux@roeck-us.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
groeck@chromium.org, Nicolas Boichat <drinkcat@chromium.org>,
linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: usbhid: do not sleep when opening device
Date: Fri, 29 May 2020 13:44:50 -0700 [thread overview]
Message-ID: <20200529204450.GA184901@roeck-us.net> (raw)
In-Reply-To: <20200529203324.GL89269@dtor-ws>
On Fri, May 29, 2020 at 01:33:24PM -0700, Dmitry Torokhov wrote:
> On Fri, May 29, 2020 at 01:14:24PM -0700, Guenter Roeck wrote:
> > On Fri, May 29, 2020 at 12:59:51PM -0700, Dmitry Torokhov wrote:
> > > usbhid tries to give the device 50 milliseconds to drain its queues
> > > when opening the device, but does it naively by simply sleeping in open
> > > handler, which slows down device probing (and thus may affect overall
> > > boot time).
> > >
> > > However we do not need to sleep as we can instead mark a point of time
> > > in the future when we should start processing the events.
> > >
> > > Reported-by: Nicolas Boichat <drinkcat@chromium.org>
> > > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > > ---
> > > drivers/hid/usbhid/hid-core.c | 27 +++++++++++++++------------
> > > drivers/hid/usbhid/usbhid.h | 1 +
> > > 2 files changed, 16 insertions(+), 12 deletions(-)
> > >
> > > diff --git a/drivers/hid/usbhid/hid-core.c b/drivers/hid/usbhid/hid-core.c
> > > index c7bc9db5b192..e69992e945b2 100644
> > > --- a/drivers/hid/usbhid/hid-core.c
> > > +++ b/drivers/hid/usbhid/hid-core.c
> > > @@ -95,6 +95,19 @@ static int hid_start_in(struct hid_device *hid)
> > > set_bit(HID_NO_BANDWIDTH, &usbhid->iofl);
> > > } else {
> > > clear_bit(HID_NO_BANDWIDTH, &usbhid->iofl);
> > > +
> > > + if (test_and_clear_bit(HID_RESUME_RUNNING,
> > > + &usbhid->iofl)) {
> > > + /*
> > > + * In case events are generated while nobody was
> > > + * listening, some are released when the device
> > > + * is re-opened. Wait 50 msec for the queue to
> > > + * empty before allowing events to go through
> > > + * hid.
> > > + */
> > > + usbhid->input_start_time = jiffies +
> > > + msecs_to_jiffies(50);
> > > + }
> > > }
> > > }
> > > spin_unlock_irqrestore(&usbhid->lock, flags);
> > > @@ -280,7 +293,8 @@ static void hid_irq_in(struct urb *urb)
> > > if (!test_bit(HID_OPENED, &usbhid->iofl))
> > > break;
> > > usbhid_mark_busy(usbhid);
> > > - if (!test_bit(HID_RESUME_RUNNING, &usbhid->iofl)) {
> > > + if (!test_bit(HID_RESUME_RUNNING, &usbhid->iofl) &&
> > > + time_after(jiffies, usbhid->input_start_time)) {
> > > hid_input_report(urb->context, HID_INPUT_REPORT,
> > > urb->transfer_buffer,
> > > urb->actual_length, 1);
> > > @@ -714,17 +728,6 @@ static int usbhid_open(struct hid_device *hid)
> > > }
> > >
> > > usb_autopm_put_interface(usbhid->intf);
> > > -
> > > - /*
> > > - * In case events are generated while nobody was listening,
> > > - * some are released when the device is re-opened.
> > > - * Wait 50 msec for the queue to empty before allowing events
> > > - * to go through hid.
> > > - */
> > > - if (res == 0)
> > > - msleep(50);
> > > -
> > Can you just set usbhid->input_start_time here ?
> > if (res == 0)
> > usbhid->input_start_time = jiffies + msecs_to_jiffies(50);
> > clear_bit(HID_RESUME_RUNNING, &usbhid->iofl);
> >
> > Then you might not need the added code in hid_start_in().
>
> That was my first version, but if hid_start_in() fails we start a timer
> and try to retry the IO (and the "res" in 0 in this case). And we want
> to mark the time only after we successfully submitted the interrupt URB,
> that is why the code is in hid_start_in().
>
Ah yes, that makes sense.
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Thanks,
Guenter
next prev parent reply other threads:[~2020-05-29 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 19:59 [PATCH] HID: usbhid: do not sleep when opening device Dmitry Torokhov
2020-05-29 20:14 ` Guenter Roeck
2020-05-29 20:33 ` Dmitry Torokhov
2020-05-29 20:44 ` Guenter Roeck [this message]
2020-05-29 23:50 ` Nicolas Boichat
2020-05-30 0:48 ` Guenter Roeck
2020-05-30 1:09 ` Dmitry Torokhov
2020-05-30 1:22 ` Guenter Roeck
2020-05-30 1:34 ` Dmitry Torokhov
2020-06-01 17:13 ` Jiri Kosina
2020-06-02 9:14 ` Benjamin Tissoires
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=20200529204450.GA184901@roeck-us.net \
--to=linux@roeck-us.net \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=drinkcat@chromium.org \
--cc=groeck@chromium.org \
--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).