[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yg0eTtiChnmfJeqX@ninjato>
Date: Wed, 16 Feb 2022 16:54:54 +0100
From: Wolfram Sang <wsa@...nel.org>
To: Matt Johnston <matt@...econstruct.com.au>
Cc: "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Jeremy Kerr <jk@...econstruct.com.au>,
linux-i2c@...r.kernel.org, netdev@...r.kernel.org,
Zev Weiss <zev@...ilderbeest.net>,
Rob Herring <robh@...nel.org>
Subject: Re: [PATCH net-next v5 1/2] dt-bindings: net: New binding
mctp-i2c-controller
On Thu, Feb 10, 2022 at 02:36:50PM +0800, Matt Johnston wrote:
> 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@...econstruct.com.au>
> Reviewed-by: Rob Herring <robh@...nel.org>
Acked-by: Wolfram Sang <wsa@...nel.org>
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists