2019-05-19 13:07:45 +01:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2016-03-10 15:35:49 -08:00
|
|
|
#
|
|
|
|
|
# RMI4 configuration
|
|
|
|
|
#
|
|
|
|
|
config RMI4_CORE
|
|
|
|
|
tristate "Synaptics RMI4 bus support"
|
2018-06-05 10:17:51 -07:00
|
|
|
select IRQ_DOMAIN
|
2016-03-10 15:35:49 -08:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to support the Synaptics RMI4 bus. This is
|
|
|
|
|
required for all RMI4 device support.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
2016-03-10 15:44:27 -08:00
|
|
|
|
2016-12-27 11:42:28 -08:00
|
|
|
if RMI4_CORE
|
|
|
|
|
|
2016-03-10 15:44:27 -08:00
|
|
|
config RMI4_I2C
|
|
|
|
|
tristate "RMI4 I2C Support"
|
2016-12-27 11:42:28 -08:00
|
|
|
depends on I2C
|
2016-03-10 15:44:27 -08:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to support RMI4 devices connected to an I2C
|
|
|
|
|
bus.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
2016-03-10 15:47:28 -08:00
|
|
|
|
2016-03-10 15:58:12 -08:00
|
|
|
config RMI4_SPI
|
|
|
|
|
tristate "RMI4 SPI Support"
|
2016-12-27 11:42:28 -08:00
|
|
|
depends on SPI
|
2016-03-10 15:58:12 -08:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to support RMI4 devices connected to a SPI
|
|
|
|
|
bus.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2016-11-08 17:05:58 -08:00
|
|
|
config RMI4_SMB
|
|
|
|
|
tristate "RMI4 SMB Support"
|
2016-12-27 11:42:28 -08:00
|
|
|
depends on I2C
|
2016-11-08 17:05:58 -08:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to support RMI4 devices connected to an SMB
|
|
|
|
|
bus.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will be
|
|
|
|
|
called rmi_smbus.
|
|
|
|
|
|
2016-12-02 16:59:07 -08:00
|
|
|
config RMI4_F03
|
2016-12-27 11:42:28 -08:00
|
|
|
bool "RMI4 Function 03 (PS2 Guest)"
|
2016-12-27 11:32:55 -08:00
|
|
|
depends on RMI4_CORE
|
2016-12-27 11:42:28 -08:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to add support for RMI4 function 03.
|
2016-12-02 16:59:07 -08:00
|
|
|
|
2016-12-27 11:42:28 -08:00
|
|
|
Function 03 provides PS2 guest support for RMI4 devices. This
|
|
|
|
|
includes support for TrackPoints on TouchPads.
|
2016-12-02 16:59:07 -08:00
|
|
|
|
2017-02-07 09:59:21 -08:00
|
|
|
config RMI4_F03_SERIO
|
|
|
|
|
tristate
|
|
|
|
|
depends on RMI4_CORE
|
|
|
|
|
depends on RMI4_F03
|
|
|
|
|
default RMI4_CORE
|
|
|
|
|
select SERIO
|
|
|
|
|
|
2016-03-10 15:47:28 -08:00
|
|
|
config RMI4_2D_SENSOR
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config RMI4_F11
|
|
|
|
|
bool "RMI4 Function 11 (2D pointing)"
|
|
|
|
|
select RMI4_2D_SENSOR
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to add support for RMI4 function 11.
|
|
|
|
|
|
|
|
|
|
Function 11 provides 2D multifinger pointing for touchscreens and
|
|
|
|
|
touchpads. For sensors that support relative pointing, F11 also
|
|
|
|
|
provides mouse input.
|
2016-03-10 15:55:29 -08:00
|
|
|
|
|
|
|
|
config RMI4_F12
|
|
|
|
|
bool "RMI4 Function 12 (2D pointing)"
|
|
|
|
|
select RMI4_2D_SENSOR
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to add support for RMI4 function 12.
|
|
|
|
|
|
|
|
|
|
Function 12 provides 2D multifinger pointing for touchscreens and
|
|
|
|
|
touchpads. For sensors that support relative pointing, F12 also
|
|
|
|
|
provides mouse input.
|
2016-03-10 15:56:58 -08:00
|
|
|
|
|
|
|
|
config RMI4_F30
|
|
|
|
|
bool "RMI4 Function 30 (GPIO LED)"
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to add support for RMI4 function 30.
|
|
|
|
|
|
|
|
|
|
Function 30 provides GPIO and LED support for RMI4 devices. This
|
|
|
|
|
includes support for buttons on TouchPads and ClickPads.
|
2016-07-18 18:10:37 -03:00
|
|
|
|
2016-11-22 17:44:12 -08:00
|
|
|
config RMI4_F34
|
|
|
|
|
bool "RMI4 Function 34 (Device reflash)"
|
|
|
|
|
select FW_LOADER
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to add support for RMI4 function 34.
|
|
|
|
|
|
|
|
|
|
Function 34 provides support for upgrading the firmware on the RMI4
|
|
|
|
|
device via the firmware loader interface. This is triggered using a
|
|
|
|
|
sysfs attribute.
|
|
|
|
|
|
2020-10-04 19:42:24 -07:00
|
|
|
config RMI4_F3A
|
|
|
|
|
bool "RMI4 Function 3A (GPIO)"
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to add support for RMI4 function 3A.
|
|
|
|
|
|
|
|
|
|
Function 3A provides GPIO support for RMI4 devices. This includes
|
|
|
|
|
support for buttons on TouchPads and ClickPads.
|
|
|
|
|
|
2016-07-18 18:10:37 -03:00
|
|
|
config RMI4_F54
|
|
|
|
|
bool "RMI4 Function 54 (Analog diagnostics)"
|
media: Kconfig: cleanup VIDEO_DEV dependencies
media Kconfig has two entries associated to V4L API:
VIDEO_DEV and VIDEO_V4L2.
On Kernel 2.6.x, there were two V4L APIs, each one with its own flag.
VIDEO_DEV were meant to:
1) enable Video4Linux and make its Kconfig options to appear;
2) it makes the Kernel build the V4L core.
while VIDEO_V4L2 where used to distinguish between drivers that
implement the newer API and drivers that implemented the former one.
With time, such meaning changed, specially after the removal of
all V4L version 1 drivers.
At the current implementation, VIDEO_DEV only does (1): it enables
the media options related to V4L, that now has:
menu "Video4Linux options"
visible if VIDEO_DEV
source "drivers/media/v4l2-core/Kconfig"
endmenu
but it doesn't affect anymore the V4L core drivers.
The rationale is that the V4L2 core has a "soft" dependency
at the I2C bus, and now requires to select a number of other
Kconfig options:
config VIDEO_V4L2
tristate
depends on (I2C || I2C=n) && VIDEO_DEV
select RATIONAL
select VIDEOBUF2_V4L2 if VIDEOBUF2_CORE
default (I2C || I2C=n) && VIDEO_DEV
In the past, merging them would be tricky, but it seems that it is now
possible to merge those symbols, in order to simplify V4L dependencies.
Let's keep VIDEO_DEV, as this one is used on some make *defconfig
configurations.
Suggested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Jacopo Mondi <jacopo@jmondi.org>
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com> # for meson-vdec & meson-ge2d
Acked-by: Andrzej Pietrasiewicz <andrzejtp2010@gmail.com>
Acked-by: Łukasz Stelmach <l.stelmach@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
2022-03-13 07:25:46 +01:00
|
|
|
depends on VIDEO_DEV=y || (RMI4_CORE=m && VIDEO_DEV=m)
|
2016-07-18 18:10:37 -03:00
|
|
|
select VIDEOBUF2_VMALLOC
|
2016-11-22 17:57:02 -08:00
|
|
|
select RMI4_F55
|
2016-07-18 18:10:37 -03:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to add support for RMI4 function 54
|
|
|
|
|
|
|
|
|
|
Function 54 provides access to various diagnostic features in certain
|
|
|
|
|
RMI4 touch sensors.
|
2016-11-22 17:53:26 -08:00
|
|
|
|
|
|
|
|
config RMI4_F55
|
|
|
|
|
bool "RMI4 Function 55 (Sensor tuning)"
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to add support for RMI4 function 55
|
|
|
|
|
|
|
|
|
|
Function 55 provides access to the RMI4 touch sensor tuning
|
|
|
|
|
mechanism.
|
2016-12-27 11:42:28 -08:00
|
|
|
|
|
|
|
|
endif # RMI_CORE
|
