All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Härdeman" <david@hardeman.nu>
To: linux-media@vger.kernel.org
Cc: sean@mess.org, mchehab@osg.samsung.com
Subject: [PATCH 0/2] NEC scancodes and protocols in keymaps
Date: Thu, 02 Apr 2015 14:02:57 +0200	[thread overview]
Message-ID: <20150402120047.20068.31662.stgit@zeus.muc.hardeman.nu> (raw)

The following two patches should show more clearly what I mean by
adding protocols to the keytables (and letting userspace add
keytable entries with explicit protocol information). Consider
it a basis for discussion.

Each patch has a separate description, please refer to those for
more information.

---

David Härdeman (2):
      rc-core: use the full 32 bits for NEC scancodes
      rc-core: don't throw away protocol information


 drivers/media/rc/ati_remote.c            |    1 
 drivers/media/rc/imon.c                  |    7 +
 drivers/media/rc/ir-nec-decoder.c        |   26 ---
 drivers/media/rc/rc-main.c               |  233 ++++++++++++++++++++++++------
 drivers/media/usb/dvb-usb-v2/af9015.c    |   22 +--
 drivers/media/usb/dvb-usb-v2/af9035.c    |   23 +--
 drivers/media/usb/dvb-usb-v2/az6007.c    |   16 +-
 drivers/media/usb/dvb-usb-v2/rtl28xxu.c  |   20 +--
 drivers/media/usb/dvb-usb/dib0700_core.c |   24 +--
 drivers/media/usb/em28xx/em28xx-input.c  |   37 +----
 include/media/rc-core.h                  |   26 +++
 include/media/rc-map.h                   |   23 ++-
 12 files changed, 264 insertions(+), 194 deletions(-)

--
David Härdeman

             reply	other threads:[~2015-04-02 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 12:02 David Härdeman [this message]
2015-04-02 12:03 ` [PATCH 1/2] rc-core: use the full 32 bits for NEC scancodes David Härdeman
2015-04-02 12:03 ` [PATCH 2/2] rc-core: don't throw away protocol information David Härdeman
2015-04-02 16:56 ` [PATCH 0/2] NEC scancodes and protocols in keymaps Mauro Carvalho Chehab
2015-04-03  7:28   ` 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=20150402120047.20068.31662.stgit@zeus.muc.hardeman.nu \
    --to=david@hardeman.nu \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=sean@mess.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.