linux-toradex.git/drivers/hid/hid-picolcd_cir.c, branch v6.11

media: rc: harmonize infrared durations to microseconds

2020-09-03T14:18:55+00:00

rc-core kapi uses nanoseconds for infrared durations for receiving, and
microseconds for sending. The uapi already uses microseconds for both,
so this patch does not change the uapi.

Infrared durations do not need nanosecond resolution. IR protocols do not
have durations shorter than about 100 microseconds. Some IR hardware offers
250 microseconds resolution, which is sufficient for most protocols.
Better hardware has 50 microsecond resolution and is enough for every
protocol I am aware off.

Unify on microseconds everywhere. This simplifies the code since less
conversion between microseconds and nanoseconds needs to be done.

This affects:
 - rx_resolution member of struct rc_dev
 - timeout member of struct rc_dev
 - duration member in struct ir_raw_event

Cc: "Bruno Prémont" 
Cc: Hans Verkuil 
Cc: Maxim Levitsky 
Cc: Patrick Lerda 
Cc: Kevin Hilman 
Cc: Neil Armstrong 
Cc: Jerome Brunet 
Cc: Martin Blumenstingl 
Cc: Sean Wang 
Cc: Matthias Brugger 
Cc: Patrice Chotard 
Cc: Maxime Ripard 
Cc: Chen-Yu Tsai 
Cc: "David Härdeman" 
Cc: Benjamin Valentin 
Cc: Antti Palosaari 
Signed-off-by: Sean Young 
Signed-off-by: Mauro Carvalho Chehab

treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 265

2019-06-05T15:30:28+00:00

Based on 1 normalized pattern(s):

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license as published by
  the free software foundation version 2 of the license this driver is
  distributed in the hope that it will be useful but without any
  warranty without even the implied warranty of merchantability or
  fitness for a particular purpose see the gnu general public license
  for more details you should have received a copy of the gnu general
  public license along with this software if not see http www gnu org
  licenses

extracted by the scancode license scanner the SPDX license identifier

  GPL-2.0-only

has been chosen to replace the boilerplate/reference in 8 file(s).

Signed-off-by: Thomas Gleixner 
Reviewed-by: Richard Fontana 
Reviewed-by: Allison Randal 
Reviewed-by: Alexios Zavras 
Cc: linux-spdx@vger.kernel.org
Link: https://lkml.kernel.org/r/20190529141333.861653206@linutronix.de
Signed-off-by: Greg Kroah-Hartman

media: rc: Remove init_ir_raw_event and DEFINE_IR_RAW_EVENT macros

2018-10-04T18:22:27+00:00

This can be done with c99 initializers, which makes the code cleaner
and more transparent. It does require gcc 4.6, because of this bug
in earlier versions:

	https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10676

Since commit cafa0010cd51 ("Raise the minimum required gcc version to
4.6"), this is the case.

Signed-off-by: Sean Young 
Signed-off-by: Mauro Carvalho Chehab

media: rc: rename RC_TYPE_* to RC_PROTO_* and RC_BIT_* to RC_PROTO_BIT_*

2017-08-20T14:02:48+00:00

RC_TYPE is confusing and it's just the protocol. So rename it.

Suggested-by: Hans Verkuil 
Signed-off-by: Sean Young 
Acked-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

media: rc-core: rename input_name to device_name

2017-08-20T13:43:52+00:00

When an ir-spi is registered, you get this message.

rc rc0: Unspecified device as /devices/platform/soc/3f215080.spi/spi_master/spi32766/spi32766.128/rc/rc0

"Unspecified device" refers to input_name, which makes no sense for IR
TX only devices. So, rename to device_name.

Also make driver_name const char* so that no casts are needed anywhere.

Now ir-spi reports:

rc rc0: IR SPI as /devices/platform/soc/3f215080.spi/spi_master/spi32766/spi32766.128/rc/rc0

Signed-off-by: Sean Young 
Signed-off-by: Mauro Carvalho Chehab

[media] rc-main: assign driver type during allocation

2017-01-30T15:59:57+00:00

The driver type can be assigned immediately when an RC device
requests to the framework to allocate the device.

This is an 'enum rc_driver_type' data type and specifies whether
the device is a raw receiver or scancode receiver. The type will
be given as parameter to the rc_allocate_device device.

Change accordingly all the drivers calling rc_allocate_device()
so that the device type is specified during the rc device
allocation. Whenever the device type is not specified, it will be
set as RC_DRIVER_SCANCODE which was the default '0' value.

Suggested-by: Sean Young 
Signed-off-by: Andi Shyti 
Signed-off-by: Sean Young 
Signed-off-by: Mauro Carvalho Chehab

[media] rc: raw IR drivers cannot handle cec, unknown or other

2017-01-30T14:40:50+00:00

unknown and other are for IR protocols for which we have no decoder,
so the raw IR drivers have no chance of generating them. cec is not
an IR protocol.

Signed-off-by: Sean Young 
Cc: Jiri Kosina 
Cc: Benjamin Tissoires 
Cc: Bruno Prémont 
Signed-off-by: Mauro Carvalho Chehab

HID: picoLCD: Deletion of unnecessary checks before three function calls

2015-06-29T12:51:12+00:00

The functions backlight_device_unregister(), lcd_device_unregister() and
rc_unregister_device() test whether their argument is NULL and then
return immediately. Thus the test around the call is not needed.

This issue was detected by using the Coccinelle software.

Signed-off-by: Markus Elfring 
Reviewed-by: Bruno Prémont 
Signed-off-by: Jiri Kosina

[media] rc-core: remove protocol arrays

2014-07-25T22:10:43+00:00

The basic API of rc-core used to be:

	dev = rc_allocate_device();
	dev->x = a;
	dev->y = b;
	dev->z = c;
	rc_register_device();

which is a pretty common pattern in the kernel, after the introduction of
protocol arrays the API looks something like:

	dev = rc_allocate_device();
	dev->x = a;
	rc_set_allowed_protocols(dev, RC_BIT_X);
	dev->z = c;
	rc_register_device();

There's no real need for the protocols to be an array, so change it
back to be consistent (and in preparation for the following patches).

[m.chehab@samsung.com: added missing changes at some files]
Signed-off-by: David Härdeman 
Signed-off-by: Mauro Carvalho Chehab

[media] rc: abstract access to allowed/enabled protocols

2014-03-11T16:24:39+00:00

The allowed and enabled protocol masks need to be expanded to be per
filter type in order to support wakeup filter protocol selection. To
ease that process abstract access to the rc_dev::allowed_protos and
rc_dev::enabled_protocols members with inline functions.

Signed-off-by: James Hogan 
Reviewed-by: Antti Seppälä 
Signed-off-by: Mauro Carvalho Chehab