From: Sean Young <sean@mess.org>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: linux-media@vger.kernel.org, "David Härdeman" <david@hardeman.nu>
Subject: [RFC PATCH 0/6] Send and receive decoded IR using lirc interface
Date: Thu, 19 Mar 2015 21:50:11 +0000 [thread overview]
Message-ID: <cover.1426801061.git.sean@mess.org> (raw)
This patch series tries to fix the lirc interface and extend it so it can
be used to send/recv scancodes in addition to raw IR:
- Make it possible to receive scancodes from hardware that generates
scancodes (with rc protocol information)
- Make it possible to receive decoded scancodes from raw IR, from the
in-kernel decoders (not mce mouse/keyboard). Now you can take any
remote, run ir-rec and you will get both the raw IR and the decoded
scancodes plus rc protocol information.
- Make it possible to send scancodes; in kernel-encoding of IR
- Make it possible to send scancodes for hardware that can only do that
(so that lirc_zilog can be moved out of staging, not completed yet)
- Possibly the lirc interface can be used for cec?
This requires a little refactoring.
- All rc-core devices will have a lirc device associated with them
- The rc-core <-> lirc bridge no longer is a "decoder", this never made
sense and caused confusion
This requires new API for rc-core lirc devices.
- New feature LIRC_CAN_REC_SCANCODE and LIRC_CAN_SEND_SCANCODE
- REC_MODE and SEND_MODE do not enable LIRC_MODE_SCANCODE by default since
this would confuse existing userspace code
- For each scancode we need:
- rc protocol (RC_TYPE_*)
- toggle and repeat bit for some protocols
- 32 bit scancode
A separate patch will introduce new v4l-utils tools ir-rec and ir-send for
displaying and sending IR, raw or scancode.
There are few FIXMEs in the code, I am sending this for early feedback. For
example there are no encoders for most IR protocols (just nec).
However the first four patches can be merged as-is should it be accepted.
Sean Young (6):
[PATCH 1/6] [media] lirc: remove broken features
[PATCH 2/6] [media] lirc: LIRC_[SG]ET_SEND_MODE should return -ENOSYS
[PATCH 3/6] [media] rc: lirc bridge should not be a raw decoder
[PATCH 4/6] [media] rc: lirc is not a protocol or a keymap
[PATCH 5/6] [media] lirc: pass IR scancodes to userspace via lirc
bridge
[PATCH 6/6] [media] rc: teach lirc how to send scancodes
.../DocBook/media/v4l/lirc_device_interface.xml | 82 ++++----
drivers/media/rc/Kconfig | 19 +-
drivers/media/rc/Makefile | 6 +-
drivers/media/rc/ir-lirc-codec.c | 211 ++++++++++++---------
drivers/media/rc/ir-nec-decoder.c | 50 +++++
drivers/media/rc/keymaps/Makefile | 1 -
drivers/media/rc/keymaps/rc-lirc.c | 42 ----
drivers/media/rc/lirc_dev.c | 18 +-
drivers/media/rc/rc-core-priv.h | 43 +++--
drivers/media/rc/rc-ir-raw.c | 23 ++-
drivers/media/rc/rc-main.c | 29 ++-
drivers/media/rc/st_rc.c | 2 +-
include/media/lirc.h | 31 ++-
include/media/rc-core.h | 9 +
include/media/rc-map.h | 42 ++--
15 files changed, 336 insertions(+), 272 deletions(-)
delete mode 100644 drivers/media/rc/keymaps/rc-lirc.c
--
2.1.0
next reply other threads:[~2015-03-19 21:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 21:50 Sean Young [this message]
2015-03-19 21:50 ` [RFC PATCH 1/6] [media] lirc: remove broken features Sean Young
2015-05-14 16:39 ` Mauro Carvalho Chehab
2015-03-19 21:50 ` [RFC PATCH 2/6] [media] lirc: LIRC_[SG]ET_SEND_MODE should return -ENOSYS Sean Young
2015-05-14 17:00 ` Mauro Carvalho Chehab
2015-03-19 21:50 ` [RFC PATCH 3/6] [media] rc: lirc bridge should not be a raw decoder Sean Young
2015-05-14 16:47 ` Mauro Carvalho Chehab
2015-03-19 21:50 ` [RFC PATCH 4/6] [media] rc: lirc is not a protocol or a keymap Sean Young
2015-05-14 16:51 ` Mauro Carvalho Chehab
2015-05-19 20:34 ` David Härdeman
2015-05-20 8:19 ` Mauro Carvalho Chehab
2015-05-20 8:49 ` David Härdeman
2015-05-20 9:01 ` Mauro Carvalho Chehab
2015-05-20 9:06 ` David Härdeman
2015-05-20 19:16 ` David Härdeman
2015-05-20 20:54 ` David Härdeman
2015-03-19 21:50 ` [RFC PATCH 5/6] [media] lirc: pass IR scancodes to userspace via lirc bridge Sean Young
2015-05-14 16:58 ` Mauro Carvalho Chehab
2015-03-19 21:50 ` [RFC PATCH 6/6] [media] rc: teach lirc how to send scancodes Sean Young
2015-05-14 17:04 ` Mauro Carvalho Chehab
2015-05-20 8:53 ` David Härdeman
2015-05-20 9:08 ` Mauro Carvalho Chehab
2015-05-20 9:18 ` David Härdeman
2015-03-30 21:18 ` [RFC PATCH 0/6] Send and receive decoded IR using lirc interface David Härdeman
2015-03-30 23:08 ` Sean Young
2015-04-01 20:33 ` David Härdeman
2015-03-31 23:47 ` Mauro Carvalho Chehab
2015-04-01 22:19 ` David Härdeman
2015-04-01 23:10 ` Mauro Carvalho Chehab
2015-04-01 23:55 ` David Härdeman
2015-04-02 11:37 ` David Härdeman
2015-04-03 10:11 ` Sean Young
2015-04-03 18:41 ` David Härdeman
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.1426801061.git.sean@mess.org \
--to=sean@mess.org \
--cc=david@hardeman.nu \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.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).