From: Rob Herring <robh@kernel.org>
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: devicetree@vger.kernel.org, linux-i2c@vger.kernel.org,
Jeremy Kerr <jk@codeconstruct.com.au>
Subject: Re: [PATCH v4] dt-bindings: net: New binding mctp-i2c-controller
Date: Mon, 27 Sep 2021 14:02:46 -0500 [thread overview]
Message-ID: <YVIVVkgGtlXBVizP@robh.at.kernel.org> (raw)
In-Reply-To: <20210923033406.3166902-1-matt@codeconstruct.com.au>
On Thu, 23 Sep 2021 11:34:06 +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@codeconstruct.com.au>
> ---
>
> Changes:
>
> v3->v4:
> Formatting and YAML syntax fixes, rename .yaml file to match
>
> v2->v3:
> Change the MCTP indicator to being a property on the I2C bus node.
>
> Thanks,
> Matt
>
> Documentation/devicetree/bindings/i2c/i2c.txt | 4 +
> .../bindings/net/mctp-i2c-controller.yaml | 92 +++++++++++++++++++
> 2 files changed, 96 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/mctp-i2c-controller.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-09-27 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 3:34 [PATCH v4] dt-bindings: net: New binding mctp-i2c-controller Matt Johnston
2021-09-27 19:02 ` Rob Herring [this message]
2021-09-29 20:53 ` Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YVIVVkgGtlXBVizP@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=linux-i2c@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.