14b2e6930SJeremy Kerr 24b2e6930SJeremy Kerrif MCTP 34b2e6930SJeremy Kerr 44b2e6930SJeremy Kerrmenu "MCTP Device Drivers" 54b2e6930SJeremy Kerr 6a0c2ccd9SJeremy Kerrconfig MCTP_SERIAL 7a0c2ccd9SJeremy Kerr tristate "MCTP serial transport" 8a0c2ccd9SJeremy Kerr depends on TTY 9a0c2ccd9SJeremy Kerr select CRC_CCITT 10a0c2ccd9SJeremy Kerr help 11a0c2ccd9SJeremy Kerr This driver provides an MCTP-over-serial interface, through a 12a0c2ccd9SJeremy Kerr serial line-discipline, as defined by DMTF specification "DSP0253 - 13a0c2ccd9SJeremy Kerr MCTP Serial Transport Binding". By attaching the ldisc to a serial 14a0c2ccd9SJeremy Kerr device, we get a new net device to transport MCTP packets. 15a0c2ccd9SJeremy Kerr 16a0c2ccd9SJeremy Kerr This allows communication with external MCTP endpoints which use 17a0c2ccd9SJeremy Kerr serial as their transport. It can also be used as an easy way to 18a0c2ccd9SJeremy Kerr provide MCTP connectivity between virtual machines, by forwarding 19a0c2ccd9SJeremy Kerr data between simple virtual serial devices. 20a0c2ccd9SJeremy Kerr 21a0c2ccd9SJeremy Kerr Say y here if you need to connect to MCTP endpoints over serial. To 22a0c2ccd9SJeremy Kerr compile as a module, use m; the module will be called mctp-serial. 23a0c2ccd9SJeremy Kerr 244fa9c518SMatt Johnstonconfig MCTP_SERIAL_TEST 254fa9c518SMatt Johnston bool "MCTP serial tests" if !KUNIT_ALL_TESTS 264fa9c518SMatt Johnston depends on MCTP_SERIAL=y && KUNIT=y 274fa9c518SMatt Johnston default KUNIT_ALL_TESTS 284fa9c518SMatt Johnston 29f5b8abf9SMatt Johnstonconfig MCTP_TRANSPORT_I2C 30f5b8abf9SMatt Johnston tristate "MCTP SMBus/I2C transport" 31f5b8abf9SMatt Johnston # i2c-mux is optional, but we must build as a module if i2c-mux is a module 32f5b8abf9SMatt Johnston depends on I2C_MUX || !I2C_MUX 33f5b8abf9SMatt Johnston depends on I2C 34f5b8abf9SMatt Johnston depends on I2C_SLAVE 35f5b8abf9SMatt Johnston select MCTP_FLOWS 36f5b8abf9SMatt Johnston help 37f5b8abf9SMatt Johnston Provides a driver to access MCTP devices over SMBus/I2C transport, 38f5b8abf9SMatt Johnston from DMTF specification DSP0237. A MCTP protocol network device is 39f5b8abf9SMatt Johnston created for each I2C bus that has been assigned a mctp-i2c device. 40f5b8abf9SMatt Johnston 41c8755b29SMatt Johnstonconfig MCTP_TRANSPORT_I3C 42c8755b29SMatt Johnston tristate "MCTP I3C transport" 43c8755b29SMatt Johnston depends on I3C 44c8755b29SMatt Johnston help 45c8755b29SMatt Johnston Provides a driver to access MCTP devices over I3C transport, 46c8755b29SMatt Johnston from DMTF specification DSP0233. 47c8755b29SMatt Johnston A MCTP protocol network device is created for each I3C bus 48c8755b29SMatt Johnston having a "mctp-controller" devicetree property. 49c8755b29SMatt Johnston 50*0791c032SJeremy Kerrconfig MCTP_TRANSPORT_USB 51*0791c032SJeremy Kerr tristate "MCTP USB transport" 52*0791c032SJeremy Kerr depends on USB 53*0791c032SJeremy Kerr help 54*0791c032SJeremy Kerr Provides a driver to access MCTP devices over USB transport, 55*0791c032SJeremy Kerr defined by DMTF specification DSP0283. 56*0791c032SJeremy Kerr 57*0791c032SJeremy Kerr MCTP-over-USB interfaces are peer-to-peer, so each interface 58*0791c032SJeremy Kerr represents a physical connection to one remote MCTP endpoint. 59*0791c032SJeremy Kerr 604b2e6930SJeremy Kerrendmenu 614b2e6930SJeremy Kerr 624b2e6930SJeremy Kerrendif 63