From: Simon Horman <horms@kernel.org>
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: linux-i3c@lists.infradead.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.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>,
miquel.raynal@bootlin.com
Subject: Re: [PATCH net-next v6 3/3] mctp i3c: MCTP I3C driver
Date: Tue, 17 Oct 2023 10:24:27 +0200 [thread overview]
Message-ID: <20231017082427.GH1751252@kernel.org> (raw)
In-Reply-To: <20231013040628.354323-4-matt@codeconstruct.com.au>
On Fri, Oct 13, 2023 at 12:06:25PM +0800, Matt Johnston wrote:
> Provides MCTP network transport over an I3C bus, as specified in
> DMTF DSP0233.
>
> Each I3C bus (with "mctp-controller" devicetree property) gets an
> "mctpi3cX" net device created. I3C devices are reachable as remote
> endpoints through that net device. Link layer addressing uses the
> I3C PID as a fixed hardware address for neighbour table entries.
>
> The driver matches I3C devices that have the MIPI assigned DCR 0xCC for
> MCTP.
>
> Signed-off-by: Matt Johnston <matt@codeconstruct.com.au>
Hi Matt,
one minor nit below, which you can take, leave, or leave for later
as far as I am concerned.
Overall the patch looks good to me and I see that Paolo's review of v5 has
has been addressed.
Reviewed-by: Simon Horman <horms@kernel.org>
> +/* List of mctp_i3c_busdev */
> +static LIST_HEAD(busdevs);
> +/* Protects busdevs, as well as mctp_i3c_bus.devs lists */
> +static DEFINE_MUTEX(busdevs_lock);
> +
> +struct mctp_i3c_bus {
> + struct net_device *ndev;
> +
> + struct task_struct *tx_thread;
> + wait_queue_head_t tx_wq;
> + /* tx_lock protects tx_skb and devs */
> + spinlock_t tx_lock;
> + /* Next skb to transmit */
> + struct sk_buff *tx_skb;
> + /* Scratch buffer for xmit */
> + u8 tx_scratch[MCTP_I3C_MAXBUF];
> +
> + /* Element of busdevs */
> + struct list_head list;
I am unsure if it is important, but I observe that on x86_64
list spans a cacheline.
> +
> + /* Provisioned ID of our controller */
> + u64 pid;
> +
> + struct i3c_bus *bus;
> + /* Head of mctp_i3c_device.list. Protected by busdevs_lock */
> + struct list_head devs;
> +};
...
next prev parent reply other threads:[~2023-10-17 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 4:06 [PATCH net-next v6 0/3] I3C MCTP net driver Matt Johnston
2023-10-13 4:06 ` [PATCH net-next v6 1/3] dt-bindings: i3c: Add mctp-controller property Matt Johnston
2023-10-13 4:06 ` [PATCH net-next v6 2/3] i3c: Add support for bus enumeration & notification Matt Johnston
2023-10-13 4:06 ` [PATCH net-next v6 3/3] mctp i3c: MCTP I3C driver Matt Johnston
2023-10-17 8:24 ` Simon Horman [this message]
2023-10-17 10:46 ` Paolo Abeni
2023-10-17 11:00 ` [PATCH net-next v6 0/3] I3C MCTP net driver patchwork-bot+netdevbpf
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=20231017082427.GH1751252@kernel.org \
--to=horms@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=matt@codeconstruct.com.au \
--cc=miquel.raynal@bootlin.com \
--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).