From: Heiner Kallweit <hkallweit1@gmail.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: linux-media@vger.kernel.org
Subject: [PATCH 0/3] media: rc: core: expose raw packet data via sysfs
Date: Sun, 7 Feb 2016 21:13:39 +0100 [thread overview]
Message-ID: <56B7A573.10804@gmail.com> (raw)
This patch series adds functionality for exposing raw data via sysfs
to the core. Up to 128 bytes received since the last break of >= 1s
can be read via a binary sysfs attribute.
There are two major use cases:
- getting raw data to be used for defining a wakeup sequence on chips
supporting wakeup via RC (e.g. nuvoton-cir)
- debugging and raw data analysis purposes
First user of this new feature is the nuvoton-cir driver.
Motivation for this extension is to allow for an easy way to set
wakeup sequences. There have been some attempts in the past for the
nuvoton driver but AFAICS it was never finished.
This patch series is going to be complemented with a patch for the
nuvoton-cir driver adding functionality to set a wakeup sequence
via sysfs.
Eventually setting a wakeup sequence would be as easy as:
- press key to be used for wakeup
- read raw key data from sysfs
- cut raw data after sequence length to be used
- write raw wakeup sequence to sysfs
Works fine here on a Zotac CI321 with nuvoton-cir.
Heiner Kallweit (3):
media: rc: add core functionality to store the most recent raw data
media: rc: expose most recent raw packet via sysfs
media: rc: nuvoton: expose most recent raw packet via sysfs
drivers/media/rc/nuvoton-cir.c | 2 ++
drivers/media/rc/rc-core-priv.h | 6 +++++
drivers/media/rc/rc-ir-raw.c | 34 ++++++++++++++++++++++++++
drivers/media/rc/rc-main.c | 53 +++++++++++++++++++++++++++++++++++++++++
include/media/rc-core.h | 5 +++-
5 files changed, 99 insertions(+), 1 deletion(-)
--
2.7.0
reply other threads:[~2016-02-07 20:14 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=56B7A573.10804@gmail.com \
--to=hkallweit1@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.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