diff options
| author | Benjamin Tissoires <benjamin.tissoires@redhat.com> | 2022-11-03 16:57:43 +0100 |
|---|---|---|
| committer | Jiri Kosina <jkosina@suse.cz> | 2022-11-15 16:28:28 +0100 |
| commit | 25621bcc89762fe1329ae9c9dab75bc70ef1aee0 (patch) | |
| tree | 64025970b1a5a5fd38d8343d70242db5ffa2f1d5 /drivers/hid/amd-sfh-hid | |
| parent | 9c730fe10493d309f402cbd28ad539379b13a24d (diff) | |
| download | linux-stable-25621bcc89762fe1329ae9c9dab75bc70ef1aee0.tar.gz linux-stable-25621bcc89762fe1329ae9c9dab75bc70ef1aee0.tar.bz2 linux-stable-25621bcc89762fe1329ae9c9dab75bc70ef1aee0.zip | |
HID: Kconfig: split HID support and hid-core compilation
Currently, we step into drivers/hid/ based on the value of
CONFIG_HID.
However, that value is a tristate, meaning that it can be a module.
As per the documentation, if we jump into the subdirectory by
following an obj-m, we can not compile anything inside that
subdirectory in vmlinux. It is considered as a bug.
To make things more friendly to HID-BPF, split HID (the HID core
parameter) from HID_SUPPORT (do we want any kind of HID support in the
system?), and make this new config a boolean.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/hid/amd-sfh-hid')
| -rw-r--r-- | drivers/hid/amd-sfh-hid/Kconfig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/hid/amd-sfh-hid/Kconfig b/drivers/hid/amd-sfh-hid/Kconfig index db069a83e9a2..56e473fc3c93 100644 --- a/drivers/hid/amd-sfh-hid/Kconfig +++ b/drivers/hid/amd-sfh-hid/Kconfig @@ -2,10 +2,10 @@ menu "AMD SFH HID Support" depends on X86_64 || COMPILE_TEST depends on PCI - depends on HID config AMD_SFH_HID tristate "AMD Sensor Fusion Hub" + select HID help If you say yes to this option, support will be included for the AMD Sensor Fusion Hub. |