From: Rob Herring <robh@kernel.org>
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: devicetree@vger.kernel.org, Wolfram Sang <wsa@kernel.org>,
Jeremy Kerr <jk@codeconstruct.com.au>
Subject: Re: [RFC PATCH v2 0/2] MCTP I2C devicetree binding
Date: Fri, 13 Aug 2021 11:33:54 -0500 [thread overview]
Message-ID: <YRae8tDReDS67sM4@robh.at.kernel.org> (raw)
In-Reply-To: <20210811034345.2424442-1-matt@codeconstruct.com.au>
On Wed, Aug 11, 2021 at 11:43:43AM +0800, Matt Johnston wrote:
> Hi Rob,
>
> These patches are a v2 RFC for a devicetree binding of MCTP-over-I2C
> hardware, where MCTP messages are transferred as SMBus block writes.
>
> Since v1 I've revised the description and commits to hopefully be
> clearer, and renamed the binding to indicate that it's generic for any
> I2C hardware. That should allow for any later device specific drivers -
> please let me know if I'm misunderstanding how it should be changed.
Adding 'generic' is not an improvement nor does it change anything.
Again, a protocol is not a device. We went thru the same thing with
HID-over-I2C.
There's still not any diagram to better understand what all this is.
Rob
next prev parent reply other threads:[~2021-08-13 16:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 3:43 [RFC PATCH v2 0/2] MCTP I2C devicetree binding Matt Johnston
2021-08-11 3:43 ` [RFC PATCH v2 1/2] dt-bindings: net: New binding for mctp-i2c-generic Matt Johnston
2021-08-12 12:19 ` Rob Herring
2021-08-11 3:43 ` [RFC PATCH v2 2/2] dt-bindings: net: mctp-i2c-generic: support muxes Matt Johnston
2021-08-13 16:33 ` Rob Herring [this message]
2021-08-16 7:32 ` [RFC PATCH v2 0/2] MCTP I2C devicetree binding Matt Johnston
2021-08-17 21:06 ` Rob Herring
2021-08-18 4:19 ` Matt Johnston
2021-08-20 19:25 ` Rob Herring
2021-08-23 7:51 ` Jeremy Kerr
2021-08-23 16:16 ` Rob Herring
2021-08-26 2:27 ` Matt Johnston
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=YRae8tDReDS67sM4@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=matt@codeconstruct.com.au \
--cc=wsa@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).