From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6EDA9C48BE0 for ; Thu, 20 Jun 2019 01:25:20 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 446F62166E for ; Thu, 20 Jun 2019 01:25:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="GmIWK0N5" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 446F62166E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Date:To:From:Subject:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=AeSxJsSXwcfGsxgfstZPsIQc4869Iv9m1cie2yEpmEw=; b=GmIWK0N5iG/n+a 7wrAX8jNpEh5nGWVaz1CdfNigR5SKwwSNvww/Pewlbxoj4n5/wWUsmZa+nNqmkEjFG3V7qMJ+x5OL NjF4Pkxf96Z+8C4SFgIJiJ04ZPm5rj1AuU2g7JlGHAOpmen0nOr6IinQ89GHdcVosJsxdV+GOuipm M3qmagBIpEBXpUqdZL4mujx9WzsbR9gqQ+sedZzroeJI6biG153k7tEEZuRSuIaGcNDfUy7xHZeIy 9j3E73gF9zCoynW3LA1GDeJ/l3kU1naPtOJHaJGbPQCtvHVAzyvCgpm9sXJCA3yDoY/NfT/D16i1F hyWYVCv7YIKTO7ZwRYJA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hdlpG-0000eH-G3; Thu, 20 Jun 2019 01:25:18 +0000 Received: from mx1.redhat.com ([209.132.183.28]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hdlpE-0000dx-Eg for linux-arm-kernel@lists.infradead.org; Thu, 20 Jun 2019 01:25:17 +0000 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C2744307D925; Thu, 20 Jun 2019 01:25:15 +0000 (UTC) Received: from ovpn-112-53.rdu2.redhat.com (ovpn-112-53.rdu2.redhat.com [10.10.112.53]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5B4E81001DD2; Thu, 20 Jun 2019 01:25:12 +0000 (UTC) Message-ID: <7c0e8909cee17623565ef88445b0497d5504fe1c.camel@redhat.com> Subject: Re: [PATCH v2 00/17] net: introduce Qualcomm IPA driver From: Dan Williams To: Subash Abhinov Kasiviswanathan , Arnd Bergmann Date: Wed, 19 Jun 2019 20:25:11 -0500 In-Reply-To: <2926e45fd7ff62fd7c4af9b338bf0caa@codeaurora.org> References: <380a6185-7ad1-6be0-060b-e6e5d4126917@linaro.org> <066e9b39f937586f0f922abf801351553ec2ba1d.camel@sipsolutions.net> <613cdfde488eb23d7207c7ba6258662702d04840.camel@sipsolutions.net> <6c70950d0c78bc02a3d016918ec3929e@codeaurora.org> <2926e45fd7ff62fd7c4af9b338bf0caa@codeaurora.org> User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.48]); Thu, 20 Jun 2019 01:25:16 +0000 (UTC) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190619_182516_513345_1E334A8E X-CRM114-Status: GOOD ( 17.54 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.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 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel