PD#SWPL-8050
Problem:
current driver does not support rca ir protocol
Solution:
add register setting and code for rca use REMOTE_RYPE_RCA to configure.
Verify:
G12b_W400 & tl1 x301
Change-Id: I76d860d66a43071803fb60debeafcbf18f42b283
Signed-off-by: Qianggui Song <qianggui.song@amlogic.com>
PD#SWPL-5555
Problem:
Current driver does not support both NEC and RC5
Solution:
Add a macro to depecit both NEC and RC5 state
Verify:
X301
Change-Id: I06894d033eabdb22db6e34fc2ad76e0390ef565f
Signed-off-by: Qianggui Song <qianggui.song@amlogic.com>
PD#SWPL-3543
Problem:
current driver does not support toshiba ir remote control protocol
Solution:
add register setting and decode code for toshiba protocol
use REMOTE_TYPE_TOSHIBA/REMOTE_TYPE_NEC_TOSHIBA to configure toshiba
only/toshiba and nec.
Verify:
tl1_t962x2_x301
Change-Id: Idad70c3879fad6e8267f0c4d80d2447c34114103
Signed-off-by: Qianggui Song <qianggui.song@amlogic.com>
PD#138714: initial add remote driver
temporarily disable the feature which reporting event after system resume,
and it will be enabled after the 'amlogic/pm' driver is available.
Change-Id: I57312621557f050401b5028b7607144cb9a9351f
Signed-off-by: Xingyu Chen <xingyu.chen@amlogic.com>
Add a symlink to uapi/linux/linux-event-codes.h, and include that
instead of (re)defining all the evdev type and code values in
dt-bindings/input/input.h. This way we do not need to keep all the event
codes synced manually.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Add the TI drv260x haptics/vibrator driver. This device uses the input
force feedback to produce a wave form to driver an ERM or LRA actuator
device.
The initial driver supports the devices real time playback mode. But the
device has additional wave patterns in ROM. This functionality will be
added in future patchsets.
Product data sheet is located here: http://www.ti.com/product/drv2605
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Many of Key device tree bindings uses the constant number as key code
which matches with kernel header key code and then comment as follows
for reference/better readability:
linux,code = <102>; /* KEY_HOME */
Create a DT header which defines all the key code so that DT key bindings
can use it as follows:
linux,code = <KEY_HOME>;
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Rob Herring <rob.herring@calxeda.com>
