diff options
| author |   Matt Johnston <matt@codeconstruct.com.au> | 2021-11-15 10:49:25 +0800 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2021-11-15 14:11:25 +0000 |
| commit | 0b6141eb2b14b0df03f48bd129182900078e7f90 (patch) | |
| tree | f302e75ee0e91cf396de1eb99ad993463d44087b /drivers/net/mctp/mctp-i2c.c | |
| parent | i2c: npcm7xx: Allow 255 byte block SMBus transfers (diff) | |
| download | linux-dev-0b6141eb2b14b0df03f48bd129182900078e7f90.tar.xz linux-dev-0b6141eb2b14b0df03f48bd129182900078e7f90.zip | |
dt-bindings: net: New binding mctp-i2c-controller
Used to define a local endpoint to communicate with MCTP peripherals
attached to an I2C bus. This I2C endpoint can communicate with remote
MCTP devices on the I2C bus.
In the example I2C topology below (matching the second yaml example) we
have MCTP devices on busses i2c1 and i2c6. MCTP-supporting busses are
indicated by the 'mctp-controller' DT property on an I2C bus node.
A mctp-i2c-controller I2C client DT node is placed at the top of the
mux topology, since only the root I2C adapter will support I2C slave
functionality.
.-------.
|eeprom |
.------------. .------. /'-------'
| adapter | | mux --@0,i2c5------'
| i2c1 ----.*| --@1,i2c6--.--.
|............| \'------' \ \ .........
| mctp-i2c- | \ \ \ .mctpB .
| controller | \ \ '.0x30 .
| | \ ......... \ '.......'
| 0x50 | \ .mctpA . \ .........
'------------' '.0x1d . '.mctpC .
'.......' '.0x31 .
'.......'
(mctpX boxes above are remote MCTP devices not included in the DT at
present, they can be hotplugged/probed at runtime. A DT binding for
specific fixed MCTP devices could be added later if required)
Signed-off-by: Matt Johnston <matt@codeconstruct.com.au>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions