From: Matt Johnston <matt@codeconstruct.com.au>
To: linux-i3c@lists.infradead.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jeremy Kerr <jk@codeconstruct.com.au>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: [PATCH net-next v2 0/3] I3C MCTP net driver
Date: Mon, 17 Jul 2023 12:06:35 +0800 [thread overview]
Message-ID: <20230717040638.1292536-1-matt@codeconstruct.com.au> (raw)
This series adds an I3C transport for the kernel's MCTP network
protocol. MCTP is a communication protocol between system components
(BMCs, drives, NICs etc), with higher level protocols such as NVMe-MI or
PLDM built on top of it (in userspace). It runs over various transports
such as I2C, PCIe, or I3C.
The mctp-i3c driver follows a similar approach to the kernel's existing
mctp-i2c driver, creating a "mctpi3cX" network interface for each
numbered I3C bus. Busses opt in to support by adding a "mctp-controller"
property to the devicetree:
&i3c0 {
mctp-controller;
}
The driver will bind to MCTP class devices (DCR 0xCC) that are on a
supported I3C bus. Each bus is represented by a `struct mctp_i3c_bus`
that keeps state for the network device. An individual I3C device
(struct mctp_i3c_device) performs operations using the "parent"
mctp_i3c_bus object. The I3C notify/enumeration patch is needed so that
the mctp-i3c driver can handle creating/removing mctp_i3c_bus objects as
required.
The mctp-i3c driver is using the Provisioned ID as an identifier for
target I3C devices (the neighbour address), as that will be more stable
than the I3C dynamic address. The driver internally translates that to a
dynamic address for bus operations.
The driver has been tested using an AST2600 platform. A remote endpoint
has been tested against Qemu, as well as using the target mode support
in Aspeed's vendor tree.
I've rebased to net-next since that is the faster moving tree. If I3C
maintainers would prefer I can submit the I3C bus enumeration patch
by itself and let it take another cycle to get into net-next, though
it wouldn't have any in-tree user. I'll leave that to maintainers.
Thanks,
Matt
---
v2:
- Rebased to net-next
- Removed unnecessary pr_ printing
- Fixed reverse christmas tree ordering
- Reworded DT property description to match I2C
Jeremy Kerr (1):
i3c: Add support for bus enumeration & notification
Matt Johnston (2):
dt-bindings: i3c: Add mctp-controller property
mctp i3c: MCTP I3C driver
.../devicetree/bindings/i3c/i3c.yaml | 6 +
drivers/i3c/master.c | 35 +
drivers/net/mctp/Kconfig | 9 +
drivers/net/mctp/Makefile | 1 +
drivers/net/mctp/mctp-i3c.c | 777 ++++++++++++++++++
include/linux/i3c/master.h | 11 +
6 files changed, 839 insertions(+)
create mode 100644 drivers/net/mctp/mctp-i3c.c
--
2.37.2
next reply other threads:[~2023-07-17 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 4:06 Matt Johnston [this message]
2023-07-17 4:06 ` [PATCH net-next v2 1/3] dt-bindings: i3c: Add mctp-controller property Matt Johnston
2023-07-17 6:19 ` Krzysztof Kozlowski
2023-07-19 9:10 ` Alexandre Belloni
2023-07-17 4:06 ` [PATCH net-next v2 2/3] i3c: Add support for bus enumeration & notification Matt Johnston
2023-07-19 1:57 ` Jakub Kicinski
2023-07-19 9:11 ` Alexandre Belloni
2023-07-19 9:10 ` Alexandre Belloni
2023-07-17 4:06 ` [PATCH net-next v2 3/3] mctp i3c: MCTP I3C driver Matt Johnston
2023-07-19 1:54 ` Jakub Kicinski
2023-07-19 2:00 ` Jakub Kicinski
2023-07-20 17:35 ` Simon Horman
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=20230717040638.1292536-1-matt@codeconstruct.com.au \
--to=matt@codeconstruct.com.au \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@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).