From: Jarod Wilson <jarod@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-media@vger.kernel.org, linux-input@vger.kernel.org
Subject: [PATCH 0/15] STAGING: add lirc device drivers
Date: Mon, 26 Jul 2010 19:25:46 -0400 [thread overview]
Message-ID: <20100726232546.GA21225@redhat.com> (raw)
This patch series adds the remaining lirc_foo device drivers to the staging
tree. The core lirc_dev driver and lirc headers are currently merged in a
v4l/dvb staging tree (which is pulled into linux-next), and are utilized by
way of an IR decoder/encoder bridge plugin to ir-core.
I've started porting lirc_foo drivers over to ir-core, first tackling the
lirc_mceusb and lirc_imon drivers. lirc_mceusb is no more, replaced by a
pure ir-core mceusb driver, and lirc_imon only supports the old first-gen
imon devices now, which are quite different from the current-gen ones, now
supported by a pure ir-core imon driver.
The long-term goal here is that all of these drivers should either be ported
to ir-core, or dropped entirely. Some of them (*cough* lirc_parallel *cough*)
should likely just be put out to pasture, but others are definitely still in
use by quite a few people out there. I've got hardware for another four or
five of the drivers, but not the rest, so I'm hoping that maybe people who
have the hardware will pitch in and help with the porting if the bits are
more readily available by way of the staging tree.
Drivers I have hardware for, and am thus most likely to work on porting to
ir-core before any others (and probably in this order):
- lirc_zilog
- lirc_streamzap
- lirc_i2c
- lirc_serial
- lirc_sir
Additionally, Maxim Levitsky, the author of lirc_ene0100, has already started
work on porting lirc_ene0100 to ir-core. Everything else, definitely
looking for help.
Patches:
staging/lirc: add lirc_bt829 driver
staging/lirc: add lirc_ene0100 driver
staging/lirc: add lirc_i2c driver
staging/lirc: add lirc_igorplugusb driver
staging/lirc: add lirc_imon driver
staging/lirc: add lirc_it87 driver
staging/lirc: add lirc_ite8709 driver
staging/lirc: add lirc_parallel driver
staging/lirc: add lirc_sasem driver
staging/lirc: add lirc_serial driver
staging/lirc: add lirc_sir driver
staging/lirc: add lirc_streamzap driver
staging/lirc: add lirc_ttusbir driver
staging/lirc: add lirc_zilog driver
staging/lirc: wire up Kconfig and Makefile bits
Diffstat:
drivers/staging/Kconfig | 2 +
drivers/staging/Makefile | 1 +
drivers/staging/lirc/Kconfig | 110 +++
drivers/staging/lirc/Makefile | 19 +
drivers/staging/lirc/TODO | 8 +
drivers/staging/lirc/lirc_bt829.c | 383 +++++++++
drivers/staging/lirc/lirc_ene0100.c | 646 ++++++++++++++
drivers/staging/lirc/lirc_ene0100.h | 169 ++++
drivers/staging/lirc/lirc_i2c.c | 536 ++++++++++++
drivers/staging/lirc/lirc_igorplugusb.c | 555 ++++++++++++
drivers/staging/lirc/lirc_imon.c | 1058 +++++++++++++++++++++++
drivers/staging/lirc/lirc_it87.c | 1019 +++++++++++++++++++++++
drivers/staging/lirc/lirc_it87.h | 116 +++
drivers/staging/lirc/lirc_ite8709.c | 542 ++++++++++++
drivers/staging/lirc/lirc_parallel.c | 705 ++++++++++++++++
drivers/staging/lirc/lirc_parallel.h | 26 +
drivers/staging/lirc/lirc_sasem.c | 933 +++++++++++++++++++++
drivers/staging/lirc/lirc_serial.c | 1313 +++++++++++++++++++++++++++++
drivers/staging/lirc/lirc_sir.c | 1282 ++++++++++++++++++++++++++++
drivers/staging/lirc/lirc_streamzap.c | 821 ++++++++++++++++++
drivers/staging/lirc/lirc_ttusbir.c | 397 +++++++++
drivers/staging/lirc/lirc_zilog.c | 1387
+++++++++++++++++++++++++++++++
22 files changed, 12028 insertions(+), 0 deletions(-)
--
Jarod Wilson
jarod@redhat.com
next reply other threads:[~2010-07-26 23:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 23:25 Jarod Wilson [this message]
2010-07-26 23:26 ` [PATCH 01/15] staging/lirc: add lirc_bt829 driver Jarod Wilson
2010-07-26 23:27 ` [PATCH 02/15] staging/lirc: add lirc_ene0100 driver Jarod Wilson
2010-07-26 23:28 ` [PATCH 03/15] staging/lirc: add lirc_i2c driver Jarod Wilson
2010-07-26 23:29 ` [PATCH 04/15] staging/lirc: add lirc_igorplugusb driver Jarod Wilson
2010-07-26 23:29 ` [PATCH 05/15] staging/lirc: add lirc_imon driver Jarod Wilson
2010-07-26 23:30 ` [PATCH 06/15] staging/lirc: add lirc_it87 driver Jarod Wilson
2010-07-26 23:30 ` [PATCH 07/15] staging/lirc: add lirc_ite8709 driver Jarod Wilson
2010-07-26 23:30 ` [PATCH 08/15] staging/lirc: add lirc_parallel driver Jarod Wilson
2010-07-26 23:31 ` [PATCH 09/15] staging/lirc: add lirc_sasem driver Jarod Wilson
2010-07-26 23:31 ` [PATCH 10/15] staging/lirc: add lirc_serial driver Jarod Wilson
2010-07-26 23:32 ` [PATCH 11/15] staging/lirc: add lirc_sir driver Jarod Wilson
2010-07-26 23:32 ` [PATCH 12/15] staging/lirc: add lirc_streamzap driver Jarod Wilson
2010-07-26 23:33 ` [PATCH 13/15] staging/lirc: add lirc_ttusbir driver Jarod Wilson
2010-07-26 23:34 ` [PATCH 14/15] staging/lirc: add lirc_zilog driver Jarod Wilson
2010-07-26 23:34 ` [PATCH 15/15] staging/lirc: wire up Kconfig and Makefile bits Jarod Wilson
2010-07-27 15:59 ` [PATCH 0/15] STAGING: add lirc device drivers Mauro Carvalho Chehab
2010-07-27 16:09 ` Greg KH
2010-07-27 18:24 ` Jarod Wilson
2010-07-27 19:33 ` Mauro Carvalho Chehab
2010-07-27 19:51 ` Greg KH
2010-07-28 2:17 ` Jarod Wilson
2010-07-27 18:17 ` Jarod Wilson
2010-07-27 19:24 ` Mauro Carvalho Chehab
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=20100726232546.GA21225@redhat.com \
--to=jarod@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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).