linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: linux-input@vger.kernel.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: [PATCH 0/8] ir-core improvements
Date: Thu, 8 Apr 2010 16:37:17 -0300	[thread overview]
Message-ID: <20100408163717.05c3581c@pedra> (raw)

Yet another series of ir-core improvements.

This series contain two fixes, plus those improvements:

1) sysfs: better define the behaviour for in-hardware and in-software raw
   decoders: different types require different functionalities;

2) sysfs: rename Remote Controllers as rc0, rc1, ...
   this is better than rcrcv0, rcrcv1, ..., because some devices have
   also RC transmitters, and they may share some functionality with
   the receiver. So, a receiver and a transmitter will be later be
   differenciated via the associated device nodes;

3) Rework ir-raw-event to support a third type of decoders: in-hardware
   samplers, with in-software decoders. In this case, the IR events
   (duration and type) are provided by the hardware, and the protocol
   decode is done in software.

Those are the patches from this series:

David Härdeman (2):
  V4L/DVB: rename sysfs remote controller devices from rcrcv to rc
  V4L/DVB: Teach drivers/media/IR/ir-raw-event.c to use durations

Mauro Carvalho Chehab (6):
  V4L/DVB: em28xx: fix a regression caused by the rc-map changes
  V4L/DVB: ir: Make sure that the spinlocks are properly initialized
  V4L/DVB: ir-core: Distinguish sysfs attributes for in-hardware and raw decoders
  V4L/DVB: ir-core: properly present the supported and current protocols
  V4L/DVB: ir-core: fix gcc warning noise
  V4L/DVB: ir-core: move subsystem internal calls to ir-core-priv.h

 drivers/media/IR/ir-core-priv.h             |  112 +++++++++++++
 drivers/media/IR/ir-functions.c             |    1 +
 drivers/media/IR/ir-keytable.c              |   19 ++-
 drivers/media/IR/ir-nec-decoder.c           |  241 +++++++++++----------------
 drivers/media/IR/ir-raw-event.c             |  161 ++++++++++--------
 drivers/media/IR/ir-rc5-decoder.c           |  154 +++++++++---------
 drivers/media/IR/ir-sysfs.c                 |  100 ++++++++----
 drivers/media/IR/rc-map.c                   |    3 +-
 drivers/media/video/em28xx/em28xx-input.c   |   21 ++-
 drivers/media/video/saa7134/saa7134-input.c |   11 +-
 include/media/ir-core.h                     |   81 +++-------
 11 files changed, 502 insertions(+), 402 deletions(-)
 create mode 100644 drivers/media/IR/ir-core-priv.h

                 reply	other threads:[~2010-04-08 19:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100408163717.05c3581c@pedra \
    --to=mchehab@redhat.com \
    --cc=linux-input@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).