From: "Antti Seppälä" <a.seppala@gmail.com>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: linux-media@vger.kernel.org, "Antti Seppälä" <a.seppala@gmail.com>
Subject: [RFC PATCH 1/4] rc-core: Add defintions needed for sysfs callback
Date: Mon, 20 Jan 2014 21:39:44 +0200 [thread overview]
Message-ID: <1390246787-15616-2-git-send-email-a.seppala@gmail.com> (raw)
In-Reply-To: <1390246787-15616-1-git-send-email-a.seppala@gmail.com>
Introduce a list for wake scancode values and add callback for sysfs
reads/writes.
Signed-off-by: Antti Seppälä <a.seppala@gmail.com>
---
include/media/rc-core.h | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/include/media/rc-core.h b/include/media/rc-core.h
index 2f6f1f7..6ee68ac 100644
--- a/include/media/rc-core.h
+++ b/include/media/rc-core.h
@@ -20,6 +20,7 @@
#include <linux/kfifo.h>
#include <linux/time.h>
#include <linux/timer.h>
+#include <linux/list.h>
#include <media/rc-map.h>
extern int rc_core_debug;
@@ -35,6 +36,16 @@ enum rc_driver_type {
};
/**
+ * struct rc_wakeup_scancode - represents a single IR code sample
+ * @value: scan code value
+ * @list: linked list pointer
+ */
+struct rc_wakeup_scancode {
+ u8 value;
+ struct list_head list_item;
+};
+
+/**
* struct rc_dev - represents a remote control device
* @dev: driver model's view of this device
* @input_name: name of the input child device
@@ -84,6 +95,7 @@ enum rc_driver_type {
* device doesn't interrupt host until it sees IR pulses
* @s_learning_mode: enable wide band receiver used for learning
* @s_carrier_report: enable carrier reports
+ * @s_wakeup_scancodes: set/get IR scancode to wake hardware from sleep states
*/
struct rc_dev {
struct device dev;
@@ -127,6 +139,7 @@ struct rc_dev {
void (*s_idle)(struct rc_dev *dev, bool enable);
int (*s_learning_mode)(struct rc_dev *dev, int enable);
int (*s_carrier_report) (struct rc_dev *dev, int enable);
+ int (*s_wakeup_scancodes) (struct rc_dev *dev, struct list_head *scancode_list, int write);
};
#define to_rc_dev(d) container_of(d, struct rc_dev, dev)
--
1.8.3.2
next prev parent reply other threads:[~2014-01-20 19:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 14:18 [PATCH] nuvoton-cir: Add support for user configurable wake-up codes Antti Seppälä
2014-01-15 19:35 ` Mauro Carvalho Chehab
2014-01-20 19:39 ` [RFC PATCH 0/4] rc: Adding support for sysfs wakeup scancodes Antti Seppälä
2014-01-20 19:39 ` Antti Seppälä [this message]
2014-01-20 19:39 ` [RFC PATCH 2/4] rc-core: Add support for reading/writing wakeup scancodes via sysfs Antti Seppälä
2014-01-20 19:39 ` [RFC PATCH 3/4] rc-loopback: " Antti Seppälä
2014-01-20 19:39 ` [RFC PATCH 4/4] nuvoton-cir: " Antti Seppälä
2014-01-21 12:28 ` [RFC PATCH 0/4] rc: Adding support for sysfs wakeup scancodes Sean Young
2014-01-22 15:46 ` Antti Seppälä
2014-01-22 16:29 ` Sean Young
2014-01-22 19:10 ` Antti Seppälä
2014-01-22 19:21 ` Antti Palosaari
2014-01-22 21:00 ` Sean Young
2014-01-22 22:01 ` Mauro Carvalho Chehab
2014-01-23 19:11 ` Antti Seppälä
2014-02-04 17:54 ` Mauro Carvalho Chehab
2014-02-05 7:03 ` Antti Seppälä
2014-02-05 9:36 ` Mauro Carvalho Chehab
2014-02-05 9:39 ` James Hogan
2014-02-05 9:42 ` James Hogan
2014-02-05 18:16 ` Antti Seppälä
2014-02-05 21:21 ` Mauro Carvalho Chehab
2014-02-06 10:46 ` James Hogan
2014-02-06 14:55 ` 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=1390246787-15616-2-git-send-email-a.seppala@gmail.com \
--to=a.seppala@gmail.com \
--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