From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: [PATCH v2 00/17] net: introduce Qualcomm IPA driver Date: Wed, 19 Jun 2019 20:25:11 -0500 Message-ID: <7c0e8909cee17623565ef88445b0497d5504fe1c.camel@redhat.com> References: <380a6185-7ad1-6be0-060b-e6e5d4126917@linaro.org> <066e9b39f937586f0f922abf801351553ec2ba1d.camel@sipsolutions.net> <613cdfde488eb23d7207c7ba6258662702d04840.camel@sipsolutions.net> <6c70950d0c78bc02a3d016918ec3929e@codeaurora.org> <2926e45fd7ff62fd7c4af9b338bf0caa@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2926e45fd7ff62fd7c4af9b338bf0caa@codeaurora.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Subash Abhinov Kasiviswanathan , Arnd Bergmann Cc: DTML , syadagir@codeaurora.org, Eric Caruso , David Miller , linux-arm-msm@vger.kernel.org, Ilias Apalodimas , Linux Kernel Mailing List , evgreen@chromium.org, Bjorn Andersson , Networking , Linux ARM , Alex Elder , Johannes Berg , linux-soc@vger.kernel.org, abhishek.esse@gmail.com, cpratapa@codeaurora.org, Ben Chan List-Id: devicetree@vger.kernel.org On Wed, 2019-06-19 at 12:47 -0600, Subash Abhinov Kasiviswanathan wrote: > > > There is a n:1 relationship between rmnet and IPA. > > > rmnet does the de-muxing to multiple netdevs based on the mux id > > > in the MAP header for RX packets and vice versa. > > > > Oh, so you mean that even though IPA supports multiple channels > > and multiple netdev instances for a physical device, all the > > rmnet devices end up being thrown into a single channel in IPA? > > > > What are the other channels for in IPA? I understand that there > > is one channel for commands that is separate, while the others > > are for network devices, but that seems to make no sense if > > we only use a single channel for rmnet data. > > > > AFAIK, the other channels are for use cases like tethering. > There is only a single channel which is used for RX > data which is then de-muxed using rmnet. That seems odd, since tethering is no different than any other data channel in QMI, just that it may have a different APN and QoS guarantees. Dan