From: Peter Mamonov <pmamonov@gmail.com>
To: barebox@lists.infradead.org
Subject: [RFC v3 0/2] WIP: add usb keyboard driver
Date: Wed, 16 Sep 2015 16:13:29 +0300 [thread overview]
Message-ID: <1442409211-23121-1-git-send-email-pmamonov@gmail.com> (raw)
Changes since v2:
ehci-hcd:
* no need for non-interruptible mdelay()
* use dev_dbg(), dev_err() functions for messages output
* remove excessive checks of pointers
* use dma_alloc_coherent for memory allocation
* use somewhat meaningful return values instead of -1
* remove too optimistic comments from the code
usb_kbd:
* allocate usb_kbd_pdata.new using dma_alloc_coherent()
* fall back to polling via control EP if interrupt polling fails
Peter Mamonov (2):
usb: ehci-hcd: port periodic transactions implementation
input: port usb keyboard driver from the u-boot
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2015-09-16 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 13:13 Peter Mamonov [this message]
2015-09-16 13:13 ` [PATCH 1/2] usb: ehci-hcd: port periodic transactions implementation from the u-boot Peter Mamonov
2015-09-16 13:13 ` [PATCH 2/2] input: port usb keyboard driver " Peter Mamonov
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=1442409211-23121-1-git-send-email-pmamonov@gmail.com \
--to=pmamonov@gmail.com \
--cc=barebox@lists.infradead.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