[PATCH v2 2/4] net: qrtr: Assign unique node id for MHI endpoints
Youssef Samir
youssef.abdulrahman at oss.qualcomm.com
Fri Sep 25 05:46:34 PDT 2026
On Thu, Sep 24, 2026 at 4:58 PM Manivannan Sadhasivam <mani at kernel.org> wrote:
>
> On Wed, Sep 23, 2026 at 04:03:38PM +0100, Youssef Samir wrote:
> > On Tue, Sep 22, 2026 at 6:24 PM Juha-Matti Tilli
> > <juha-matti.tilli at iki.fi> wrote:
> > >
> > > On Tue, Sep 22, 2026, at 20:14, Youssef Samir wrote:
> > > > On 9/21/2026 12:23 PM, Manivannan Sadhasivam via B4 Relay wrote:
> > > > > +
> > The chance of collision is slim, but still not impossible.
>
> When you mean collision, do you mean node id collision due to bridged nodes?
> Because, even if the directly connected QAIC devices use 32bit node ids, the
> collision won't affect the functionality.
As in ep_nid of one device matching the nid of another device. In MHI,
that shouldn't
really matter since this patch moves away from using QRTR_EP_NID_AUTO in node
assignment, but as you mentioned below, it could clash with TUN and SMD EPs that
are already registered with their ep_nid.
>
> Also, there is a collision with SMD and TUN endpoints, but that's out of scope
> for this series.
I have not worked on a system that simultaneously uses different types of EPs;
only MHI EPs. But if there is a real case of that, we can move to
global ID assignment
that includes SMD and TUN.
Thanks,
Youssef
More information about the ath12k
mailing list