All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@redhat.com>
To: linux-media@vger.kernel.org
Subject: [PATCH v2 0/3] IR: add lirc support to ir-core
Date: Sat, 3 Jul 2010 00:05:30 -0400	[thread overview]
Message-ID: <20100703040530.GB31255@redhat.com> (raw)
In-Reply-To: <20100601205005.GA28322@redhat.com>

On Tue, Jun 01, 2010 at 04:50:05PM -0400, Jarod Wilson wrote:
> This patch series adds the core lirc device interface, lirc_dev, and
> an ir-core bridge driver. Currently, only the receive side is wired
> up in the bridge driver, but adding transmit support is up next.
> 
> Currently, adding this code allows any raw IR ir-core device driver to
> pass raw IR out to the lirc userspace, without the driver having to have
> any actual knowledge of lirc -- its just feeding data to another IR
> protocol decoder engine.
> 
> This also (hopefully) makes life easier for any currently out-of-tree
> pure lirc device drivers, as they can count on the lirc core bits being
> present. This is a Good Thing(tm) while we work on porting additional
> lirc device drivers to ir-core, and also makes life easier for users to
> migrate from lirc decoding to in-kernel decoding (where possible) when
> their device's driver gets ported.
> 
> This patchset has been tested with the ir-core mceusb driver, and IR
> receive behaves 100% identical in lirc mode to the old lirc_mceusb.
> 
> [PATCH 1/3] IR: add core lirc device interface
> [PATCH 2/3] IR: add an empty lirc "protocol" keymap
> [PATCH 3/3] IR: add ir-core to lirc interface bridge driver

Version 2 moves a good chunk of ir tx details that are (probably) specific
to providing raw IR data from userspace via lirc into the ir-core lirc
bridge driver, instead of having them in the hardware-specific drivers
themselves. This greatly reduced the complexity of the mceusb driver's ir
tx function, and generalized the tx interface better for a non-lirc tx
implementation.

-- 
Jarod Wilson
jarod@redhat.com


  parent reply	other threads:[~2010-07-03  4:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 20:50 [PATCH 0/3] IR: add lirc support to ir-core Jarod Wilson
2010-06-01 20:51 ` [PATCH 1/3] IR: add core lirc device interface Jarod Wilson
2010-06-03  6:02   ` Mauro Carvalho Chehab
2010-06-03 22:06     ` Jarod Wilson
2010-06-04  4:10       ` Mauro Carvalho Chehab
2010-06-04 15:51         ` Christoph Bartelmus
2010-06-04 18:38           ` Mauro Carvalho Chehab
2010-06-04 18:57             ` Jon Smirl
2010-06-04 20:17               ` Jarod Wilson
2010-06-04 21:17                 ` Jarod Wilson
2010-06-04 23:16                   ` Jon Smirl
2010-06-05  2:45                     ` Jarod Wilson
2010-06-05 12:43                       ` Jarod Wilson
2010-06-05 17:43                     ` Stefan Richter
2010-06-05 17:24               ` Andy Walls
2010-06-05 17:52                 ` Jon Smirl
2010-06-07 18:44             ` David Härdeman
2010-06-07 19:45               ` Jarod Wilson
2010-06-08 17:40                 ` David Härdeman
2010-07-03  3:27             ` Jarod Wilson
2010-06-01 20:52 ` [PATCH 2/3] IR: add an empty lirc "protocol" keymap Jarod Wilson
2010-06-01 20:52 ` [PATCH 3/3] IR: add ir-core to lirc interface bridge driver Jarod Wilson
2010-07-03  4:05 ` Jarod Wilson [this message]
2010-07-03  4:06   ` [PATCH 1/3] IR: add lirc device interface Jarod Wilson
2010-07-03  4:07   ` [PATCH v2 2/3] IR: add ir-core to lirc userspace decoder bridge driver Jarod Wilson
2010-07-03  4:08   ` [PATCH v2 3/3] IR: add empty lirc pseudo-keymap Jarod Wilson
2010-07-03  4:10   ` [PATCH 4/3] IR/lirc: add docbook info covering lirc device interface Jarod Wilson
2010-07-04 15:31     ` 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=20100703040530.GB31255@redhat.com \
    --to=jarod@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.