Re: [PATCH net-next 0/2] net: mctp: Add MCTP transport for the Axiado AX3005 IRoT

From: Jeremy Kerr

Date: Mon Nov 16 2026 - 09:08:29 EST


Hi Akhila,

> Thanks for the review. To give some context first: this link is
> entirely internal to the AX3005, and not for host communication. The
> IRoT's MCTP endpoint is only reachable from the application subsystem
> on the same die, through the mailbox and the shared-memory carve-out.

Yep, understood.

> Both ends are fixed on the same die, and no third-party MCTP device
> can ever be on the other end of this link, so carrying it as MMBI
> would add nothing.

It would mean that the driver doesn't need to be entirely custom.

I'm mainly curious as to why you went with a brand-new interface rather
than implement MMBI.

> The IRoT can't bridge anything to this link. As above, nothing outside
> the chip has a hardware path to the IRoT's MCTP endpoint, so the
> application processor is its only MCTP peer.

OK, makes sense. Be aware that you may have the other direction too, in
which case the iRoT may need to fragment (and reassemble) packets that
are bridged through this host, to other peers via links with a smaller
MTU.

I assume that's not in your current designs, but will crop up if those
change.

> If you would prefer, v2 can default mtu to the 68-byte baseline and
> leave max_mtu at the negotiated limit, so the platform config raises
> it explicitly. I'm fine with either option.

Your call really. It's generally safer to start at the BTU and then
increase, but if your platform design means that the max MTU will always
be safe, then may as well set that.

> Please send the implementation comments when you're ready; I'll fold
> them into v2.

OK, shall do.

Cheers,


Jeremy