summaryrefslogtreecommitdiff
path: root/drivers/i3c/Kconfig
blob: 93e6c1e68a2b5711d2b03f793957f001ff44a33d (plain)
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
46
47
48
49
50
51
52
53
# SPDX-License-Identifier: GPL-2.0

menuconfig I3C
	tristate "I3C support"
	select I2C
	help
	  I3C is a serial protocol standardized by the MIPI alliance.

	  It's supposed to be backward compatible with I2C while providing
	  support for high speed transfers and native interrupt support
	  without the need for extra pins.

	  The I3C protocol also standardizes the slave device types and is
	  mainly designed to communicate with sensors.

	  If you want I3C support, you should say Y here and also to the
	  specific driver for your bus adapter(s) below.

	  This I3C support can also be built as a module.  If so, the module
	  will be called i3c.

if I3C

source "drivers/i3c/mctp/Kconfig"

config I3CDEV
	tristate "I3C device interface"
	depends on I3C
	help
	  Say Y here to use i3c-* device files, usually found in the /dev
	  directory on your system.  They make it possible to have user-space
	  programs use the I3C devices.

	  This support is also available as a module.  If so, the module
	  will be called i3cdev.

	  Note that this application programming interface is EXPERIMENTAL
	  and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.

config I3C_HUB
	tristate "I3C HUB support"
	depends on I3C
	select REGMAP_I3C
	help
	  This enables support for I3C HUB. Say Y here to use I3C HUB driver to
	  configure I3C HUB device.

	  I3C HUB drivers will be loaded automatically when I3C device with BCR
	  equals to 0xC2 (HUB device) is detected on the bus.

source "drivers/i3c/master/Kconfig"

endif # I3C