Netdev List
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Juha-Matti Tilli <juha-matti.tilli@iki.fi>,
	Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	Jeff Johnson <jjohnson@kernel.org>,
	linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	ath11k@lists.infradead.org, ath12k@lists.infradead.org,
	Bjorn Andersson <andersson@kernel.org>,
	Chris Lew <christopher.lew@oss.qualcomm.com>,
	Raj Kumar Bhagat <raj.bhagat@oss.qualcomm.com>,
	Jeff Hugo <jeff.hugo@oss.qualcomm.com>
Subject: Re: [PATCH v3 2/4] net: qrtr: Assign unique node id for MHI endpoints
Date: Tue, 29 Sep 2026 22:37:34 +0200	[thread overview]
Message-ID: <10091679-7567-42C2-B77E-EFD95CEDD649@holtmann.org> (raw)
In-Reply-To: <m657dtesuagn7vdajsuzjb4mfysf5xabsu3s6n6lujj7yb3z4p@m2e7e3n4zyev>

Hi Mani,

>>>>> +#define QRTR_NODE_HOST_BASE 0x10000u
>>>> 
>>>> Can it be exposed with include/uapi/linux/qrtr.h also. There are user space clients like modem manager
>>>> which need to calculate modified node id to distinguish same service from multi modem over mhi.
>>>> This is same as wlan use case.
>>> 
>>> did anybody actually looked at the proposal that Denis and I came up with. It was exactly addressing this properly.
>>> 
>>> It seems you guys came up with some hot fix and want to run with it. After month and month of silence and not bothering to review the proposal, you are trying to push your thing?
>>> 
>>> If you don’t support userspace, your proposal is broken. Plain and simple.
>> 
>> I'm still willing to submit a new version of that patchset originally by
>> Denis, if the kernel devs so decide that it's the way. For example, the
>> "radix tree of radix trees" approach could be replaced with a hash
>> table.
>> 
>> There was also some criticism about a layering violation in storing the
>> endpoint id to mhi controller. However, maybe that could be reduced by
>> providing a correct abstraction around it, so that other code doesn't
>> touch the mhi controller structure directly.
>> 
>> Other criticism for that patchset by Denis was its overt complexity.
>> Yes, it has more lines of code changed.
>> 
>> This dual-card setup needs to be handled somehow, either by Denis's
>> patchset or by Manivannan's patchset.
>> 
> 
> I wish to go ahead with my series as it is simple and tested across the
> multi-WLAN setups. For concern around exposing the nid to userspace, I'll
> implement it in next version, thanks!

actually no. Seems you have no plan on how to address the userspace problem.

It would be useful to actually review the endpoint_id concept introduced by Denis since it has a userspace facing API. What is your plan? Are you planning to break all existing userspace code?

Regards

Marcel


  reply	other threads:[~2026-09-29 20:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 13:41 [PATCH v3 0/4] net: qrtr: Add support for using identical MHI endpoint devices Manivannan Sadhasivam via B4 Relay
2026-09-22 13:41 ` [PATCH v3 1/4] net: qrtr: Allow the host QRTR to assign a unique node id Manivannan Sadhasivam via B4 Relay
2026-09-25  7:43   ` netdev-bot+sashiko
2026-09-22 13:41 ` [PATCH v3 2/4] net: qrtr: Assign unique node id for MHI endpoints Manivannan Sadhasivam via B4 Relay
2026-09-25  7:43   ` netdev-bot+sashiko
2026-09-29 16:45   ` Deepak Kumar Singh
2026-09-29 17:05     ` Marcel Holtmann
2026-09-29 17:16       ` Juha-Matti Tilli
2026-09-29 17:19         ` Robert Marko
2026-09-29 19:34         ` Manivannan Sadhasivam
2026-09-29 20:37           ` Marcel Holtmann [this message]
2026-09-30  5:54             ` Juha-Matti Tilli
2026-09-30 14:33               ` Marcel Holtmann
2026-10-01 14:20                 ` Juha-Matti Tilli
2026-10-01 15:39                   ` Marcel Holtmann
2026-10-01 20:05                     ` Manivannan Sadhasivam
2026-09-29 19:32       ` Manivannan Sadhasivam
2026-09-29 19:28     ` Manivannan Sadhasivam
2026-09-22 13:41 ` [PATCH v3 3/4] wifi: ath11k: Connect to the QMI server belonging to the device owned by this driver Manivannan Sadhasivam via B4 Relay
2026-09-25  7:43   ` netdev-bot+sashiko
2026-09-22 13:41 ` [PATCH v3 4/4] wifi: ath12k: " Manivannan Sadhasivam via B4 Relay
2026-09-22 15:52   ` Raj Kumar Bhagat
2026-09-23  6:42   ` Juha-Matti Tilli
2026-09-25  7:43   ` netdev-bot+sashiko
2026-09-29  8:59 ` [PATCH v3 0/4] net: qrtr: Add support for using identical MHI endpoint devices Paolo Abeni

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=10091679-7567-42C2-B77E-EFD95CEDD649@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=andersson@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=ath12k@lists.infradead.org \
    --cc=christopher.lew@oss.qualcomm.com \
    --cc=davem@davemloft.net \
    --cc=deepak.singh@oss.qualcomm.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=jjohnson@kernel.org \
    --cc=juha-matti.tilli@iki.fi \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=raj.bhagat@oss.qualcomm.com \
    /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