Changes in Makefile

0791c032 - net: mctp: Add MCTP USB transport driver

Fri, 21 Feb 2025 00:56:58 +0000

net: mctp: Add MCTP USB transport driverAdd an implementation for DMTF DSP0283, which defines a MCTP-over-USBtransport. As per that spec, we're restricted to full speed mode,requiring 512-byte transfers.Each MCTP-over-USB interface is a peer-to-peer link to a single MCTPendpoint, so no physical addressing is required (of course, that MCTPendpoint may then bridge to further MCTP endpoints). Consequently,interfaces will report with no lladdr data: # mctp link dev lo index 1 address 00:00:00:00:00:00 net 1 mtu 65536 up dev mctpusb0 index 6 address none net 1 mtu 68 upThis is a simple initial implementation, with single rx & tx urbs, andno multi-packet tx transfers - although we do accept multi-packet rxfrom the device.Includes suggested fixes from Santosh Puranik .Signed-off-by: Jeremy Kerr Cc: Santosh Puranik Link: https://patch.msgid.link/20250221-dev-mctp-usb-v3-2-3353030fe9cc@codeconstruct.com.auSigned-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/mctp/Makefile

c8755b29 - mctp i3c: MCTP I3C driver

Fri, 13 Oct 2023 04:06:25 +0000

mctp i3c: MCTP I3C driverProvides MCTP network transport over an I3C bus, as specified inDMTF DSP0233.Each I3C bus (with "mctp-controller" devicetree property) gets an"mctpi3cX" net device created. I3C devices are reachable as remoteendpoints through that net device. Link layer addressing uses theI3C PID as a fixed hardware address for neighbour table entries.The driver matches I3C devices that have the MIPI assigned DCR 0xCC forMCTP.Signed-off-by: Matt Johnston Reviewed-by: Simon Horman Signed-off-by: Paolo Abeni List of files: /linux-6.15/drivers/net/mctp/Makefile

f5b8abf9 - mctp i2c: MCTP I2C binding driver

Fri, 18 Feb 2022 05:51:06 +0000

mctp i2c: MCTP I2C binding driverProvides MCTP network transport over an I2C bus, as specified inDMTF DSP0237. All messages between nodes are sent as SMBus Block Writes.Each I2C bus to be used for MCTP is flagged in devicetree by a'mctp-controller' property on the bus node. Each flagged bus gets amctpi2cX net device created based on the bus number. A'mctp-i2c-controller' I2C client needs to be added under the adapter. Inan I2C mux situation the mctp-i2c-controller node must be attached onlyto the root I2C bus. The I2C client will handle incoming I2C slave blockwrite data for subordinate busses as well as its own bus.In configurations without devicetree a driver instance can be attachedto a bus using the I2C slave new_device mechanism.The MCTP core will hold/release the MCTP I2C device while responsesare pending (a 6 second timeout or once a socket is closed, responsereceived etc). While held the MCTP I2C driver will lock the I2C bus sothat the correct I2C mux remains selected while responses are received.(Ideally we would just lock the mux to keep the current bus selected forthe response rather than a full I2C bus lock, but that isn't exposed inthe I2C mux API)Signed-off-by: Matt Johnston Signed-off-by: Jeremy Kerr Reviewed-by: Wolfram Sang # I2C transport partsSigned-off-by: David S. Miller List of files: /linux-6.15/drivers/net/mctp/Makefile

a0c2ccd9 - mctp: Add MCTP-over-serial transport binding

Tue, 23 Nov 2021 07:50:46 +0000

mctp: Add MCTP-over-serial transport bindingThis change adds a MCTP Serial transport binding, as defined by DMTFspecificiation DSP0253 - "MCTP Serial Transport Binding". This isimplemented as a new serial line discipline, and can be attached toarbitrary tty devices.From the Kconfig description: This driver provides an MCTP-over-serial interface, through a serial line-discipline, as defined by DMTF specification "DSP0253 - MCTP Serial Transport Binding". By attaching the ldisc to a serial device, we get a new net device to transport MCTP packets. This allows communication with external MCTP endpoints which use serial as their transport. It can also be used as an easy way to provide MCTP connectivity between virtual machines, by forwarding data between simple virtual serial devices. Say y here if you need to connect to MCTP endpoints over serial. To compile as a module, use m; the module will be called mctp-serial.Once the N_MCTP line discipline is set [using ioctl(TCIOSETD)], we get anew netdev suitable for MCTP communication.The 'mctp' utility[1] provides a simple wrapper for this ioctl, using'link serial ': # mctp link serial /dev/ttyS0 & # mctp link dev lo index 1 address 0x00:00:00:00:00:00 net 1 mtu 65536 up dev mctpserial0 index 5 address 0x(no-addr) net 1 mtu 68 down[1]: https://github.com/CodeConstruct/mctpSigned-off-by: Jeremy Kerr Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/mctp/Makefile

2f6a470d - Revert "Merge branch 'mctp-i2c-driver'"

Mon, 15 Nov 2021 15:49:46 +0000

Revert "Merge branch 'mctp-i2c-driver'"This reverts commit 71812af7234f30362b43ccff33f93890ae4c0655, reversingchanges made to cc0be1ad686fb29a4d127948486f40b17fb34b50.Wolfram Sang says:Please revert. Besides the driver in net, it modifies the I2C corecode. This has not been acked by the I2C maintainer (in this case me).So, please don't pull this in via the net tree. The question raised here(extending SMBus calls to 255 byte) is complicated because we need ABIbackwards compatibility.Link: https://lore.kernel.org/all/YZJ9H4eM%2FM7OXVN0@shikoro/Signed-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/mctp/Makefile

80be9b2c - mctp i2c: MCTP I2C binding driver

Mon, 15 Nov 2021 02:49:26 +0000

mctp i2c: MCTP I2C binding driverProvides MCTP network transport over an I2C bus, as specified inDMTF DSP0237. All messages between nodes are sent as SMBus Block Writes.Each I2C bus to be used for MCTP is flagged in devicetree by a'mctp-controller' property on the bus node. Each flagged bus gets amctpi2cX net device created based on the bus number. A'mctp-i2c-controller' I2C client needs to be added under the adapter. Inan I2C mux situation the mctp-i2c-controller node must be attached onlyto the root I2C bus. The I2C client will handle incoming I2C slave blockwrite data for subordinate busses as well as its own bus.In configurations without devicetree a driver instance can be attachedto a bus using the I2C slave new_device mechanism.The MCTP core will hold/release the MCTP I2C device while responsesare pending (a 6 second timeout or once a socket is closed, responsereceived etc). While held the MCTP I2C driver will lock the I2C bus sothat the correct I2C mux remains selected while responses are received.(Ideally we would just lock the mux to keep the current bus selected forthe response rather than a full I2C bus lock, but that isn't exposed inthe I2C mux API)This driver requires I2C adapters that allow 255 byte transfers(SMBus 3.0) as the specification requires a minimum MTU of 68 bytes.Signed-off-by: Matt Johnston Signed-off-by: Jeremy Kerr Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/mctp/Makefile

4b2e6930 - mctp: Add initial driver infrastructure

Thu, 29 Jul 2021 02:20:43 +0000

mctp: Add initial driver infrastructureAdd an empty drivers/net/mctp/, for future interface drivers.Signed-off-by: Jeremy Kerr Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/mctp/Makefile