File: Kconfig

package info (click to toggle)
linux 6.19.2-1~exp1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 1,759,612 kB
  • sloc: ansic: 27,004,852; asm: 273,402; sh: 151,313; python: 81,277; makefile: 58,544; perl: 34,311; xml: 21,064; cpp: 5,984; yacc: 4,841; lex: 2,901; awk: 1,707; sed: 30; ruby: 25
file content (45 lines) | stat: -rw-r--r-- 1,330 bytes parent folder | download | duplicates (21)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
# SPDX-License-Identifier: GPL-2.0
menuconfig GREYBUS
	tristate "Greybus support"
	depends on SYSFS
	help
	  This option enables the Greybus driver core.  Greybus is a
	  hardware protocol that was designed to provide Unipro with a
	  sane application layer.  It was originally designed for the
	  ARA project, a module phone system, but has shown up in other
	  phones, and can be tunneled over other busses in order to
	  control hardware devices.

	  Say Y here to enable support for these types of drivers.

	  To compile this code as a module, choose M here: the module
	  will be called greybus.ko

if GREYBUS

config GREYBUS_BEAGLEPLAY
	tristate "Greybus BeaglePlay driver"
	depends on SERIAL_DEV_BUS
	select CRC_CCITT
	select FW_LOADER
	select FW_UPLOAD
	help
	  Select this option if you have a BeaglePlay where CC1352
	  co-processor acts as Greybus SVC.

	  To compile this code as a module, chose M here: the module
	  will be called gb-beagleplay.ko

config GREYBUS_ES2
	tristate "Greybus ES3 USB host controller"
	depends on USB
	help
	  Select this option if you have a Toshiba ES3 USB device that
	  acts as a Greybus "host controller".  This device is a bridge
	  from a USB device to a Unipro network.

	  To compile this code as a module, choose M here: the module
	  will be called gb-es2.ko

endif	# GREYBUS