From: Sean Young <sean@mess.org>
To: linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jon Rhees <support@usbuirt.com>, Oliver Neukum <oneukum@suse.com>
Subject: [PATCH v4 0/2] IR driver for USB-UIRT device
Date: Thu, 10 Jun 2021 11:16:23 +0100 [thread overview]
Message-ID: <cover.1623318855.git.sean@mess.org> (raw)
This is a new rc-core driver for the USB-UIRT which you can see here
http://www.usbuirt.com/
This device is supported in lirc, via the usb serial kernel driver. This
driver is both for rc-core, which means it can use kernel/BPF decoding
ec. Also this implement is superior because it can:
- support learning mode
- setting transmit carrier
- larger transmits using streaming tx command
Changes since v3:
- Review comments from Johan Hovold
- Do not move the ftdi_sio.h file an copy FTDI_* definitions instead
Changes since v2:
- Fixed race condition is disconnect
- Removed superfluous kmalloc in short tx
Changes since v1:
- Review comments from Oliver Neukum
- Simplified wideband read function
Sean Young (2):
media: rc: new driver for USB-UIRT device
USB: serial: blacklist USB-UIRT when driver is selected
drivers/media/rc/Kconfig | 11 +
drivers/media/rc/Makefile | 1 +
drivers/media/rc/uirt.c | 740 ++++++++++++++++++++++++++++++++++
drivers/usb/serial/ftdi_sio.c | 6 +-
4 files changed, 756 insertions(+), 2 deletions(-)
create mode 100644 drivers/media/rc/uirt.c
--
2.31.1
next reply other threads:[~2021-06-10 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 10:16 Sean Young [this message]
2021-06-10 10:16 ` [PATCH v4 1/2] media: rc: new driver for USB-UIRT device Sean Young
2021-06-17 22:18 ` kernel test robot
2021-06-18 8:44 ` Sean Young
2021-06-18 17:04 ` Nathan Chancellor
2021-06-18 21:19 ` Sean Young
2021-06-10 10:16 ` [PATCH v4 2/2] USB: serial: blacklist USB-UIRT when driver is selected Sean Young
2021-06-10 10:23 ` Greg Kroah-Hartman
2021-06-10 10:34 ` Sean Young
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=cover.1623318855.git.sean@mess.org \
--to=sean@mess.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=support@usbuirt.com \
/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).