Kconfig 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869
  1. # SPDX-License-Identifier: GPL-2.0+
  2. # Copyright (C) 2019-2022 Maximilian Luz <luzmaximilian@gmail.com>
  3. menuconfig SURFACE_AGGREGATOR
  4. tristate "Microsoft Surface System Aggregator Module Subsystem and Drivers"
  5. depends on SERIAL_DEV_BUS
  6. depends on ACPI && !RISCV
  7. select CRC_ITU_T
  8. help
  9. The Surface System Aggregator Module (Surface SAM or SSAM) is an
  10. embedded controller (EC) found on 5th- and later-generation Microsoft
  11. Surface devices (i.e. Surface Pro 5, Surface Book 2, Surface Laptop,
  12. and newer, with exception of Surface Go series devices).
  13. Depending on the device in question, this EC provides varying
  14. functionality, including:
  15. - EC access from ACPI via Surface ACPI Notify (5th- and 6th-generation)
  16. - battery status information (all devices)
  17. - thermal sensor access (all devices)
  18. - performance mode / cooling mode control (all devices)
  19. - clipboard detachment system control (Surface Book 2 and 3)
  20. - HID / keyboard input (Surface Laptops, Surface Book 3)
  21. This option controls whether the Surface SAM subsystem core will be
  22. built. This includes a driver for the Surface Serial Hub (SSH), which
  23. is the device responsible for the communication with the EC, and a
  24. basic kernel interface exposing the EC functionality to other client
  25. drivers, i.e. allowing them to make requests to the EC and receive
  26. events from it. Selecting this option alone will not provide any
  27. client drivers and therefore no functionality beyond the in-kernel
  28. interface. Said functionality is the responsibility of the respective
  29. client drivers.
  30. Note: While 4th-generation Surface devices also make use of a SAM EC,
  31. due to a difference in the communication interface of the controller,
  32. only 5th and later generations are currently supported. Specifically,
  33. devices using SAM-over-SSH are supported, whereas devices using
  34. SAM-over-HID, which is used on the 4th generation, are currently not
  35. supported.
  36. Choose m if you want to build the SAM subsystem core and SSH driver as
  37. module, y if you want to build it into the kernel and n if you don't
  38. want it at all.
  39. config SURFACE_AGGREGATOR_BUS
  40. bool "Surface System Aggregator Module Bus"
  41. depends on SURFACE_AGGREGATOR
  42. default y
  43. help
  44. Expands the Surface System Aggregator Module (SSAM) core driver by
  45. providing a dedicated bus and client-device type.
  46. This bus and device type are intended to provide and simplify support
  47. for non-platform and non-ACPI SSAM devices, i.e. SSAM devices that are
  48. not auto-detectable via the conventional means (e.g. ACPI).
  49. config SURFACE_AGGREGATOR_ERROR_INJECTION
  50. bool "Surface System Aggregator Module Error Injection Capabilities"
  51. depends on SURFACE_AGGREGATOR
  52. depends on FUNCTION_ERROR_INJECTION
  53. help
  54. Provides error-injection capabilities for the Surface System
  55. Aggregator Module subsystem and Surface Serial Hub driver.
  56. Specifically, exports error injection hooks to be used with the
  57. kernel's function error injection capabilities to simulate underlying
  58. transport and communication problems, such as invalid data sent to or
  59. received from the EC, dropped data, and communication timeouts.
  60. Intended for development and debugging.