mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Aleksey Kuleshov <rndfax@yandex.ru>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] usb_kbd: fix overpolling of keyboard
Date: Thu, 03 Mar 2016 11:28:28 +0300	[thread overview]
Message-ID: <818051456993708@web20j.yandex.ru> (raw)
In-Reply-To: <20160303080152.GV9224@pengutronix.de>

>>  - use async callings to call poll function
>>  - remove unused
>>  - remove unnecessary locking
>
> The changes look ok, but could you split them up by logical changes?

Okay, no problem, will send ASAP.

> This patch does not solve the problem with the double return key
> detected, right?

Yes, it just fixes the way of interacting with USB keyboard by using periodic
(per several milliseconds) polling.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2016-03-03  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 10:50 Aleksey Kuleshov
2016-03-03  8:01 ` Sascha Hauer
2016-03-03  8:28   ` Aleksey Kuleshov [this message]

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=818051456993708@web20j.yandex.ru \
    --to=rndfax@yandex.ru \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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