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=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 ED2D9C282CE for ; Mon, 3 Jun 2019 19:04:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C786626DD1 for ; Mon, 3 Jun 2019 19:04:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="e9asATus"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="MoQ3CkC5" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726963AbfFCTEo (ORCPT ); Mon, 3 Jun 2019 15:04:44 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:36876 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726336AbfFCTEm (ORCPT ); Mon, 3 Jun 2019 15:04:42 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id BFD07607C3; Mon, 3 Jun 2019 19:04:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1559588681; bh=2fFF2UZ1IMZoss2BdlfTKftG1dBbtIAex7bZx7hQCNA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=e9asATusPcw0LSbghmIwPQkwJg+oAHwQGTHydazcY9tQ/gFD4R4zc69ZFUkWTLl6N EHfjekEeWo6jkd01rCHpfPFf36FY5lJUx6ICYxQfcrni/SbnVoNcA+J0/XNEgUpG03 tI4hqzXe7SRakYnfbSamFoqjH5/ujpYtpSMAF6DI= Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id 639956020A; Mon, 3 Jun 2019 19:04:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1559588677; bh=2fFF2UZ1IMZoss2BdlfTKftG1dBbtIAex7bZx7hQCNA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=MoQ3CkC5zUj8smO9TgVqkewwzN+bMdSvy1hwgvlG1qi8GDPxO9pSlf2g2VzGuEgZ7 iW1JFRDNNyJGMxrHj2N2KKQJ1R9sOPUWSN2u7qkqOAa3Cy9TTjpL7rWs/BRNAqeBdM IM1gEWYa2IWjjsaxCuJWM6r5brDVUnpN2UWV4XPM= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 03 Jun 2019 13:04:37 -0600 From: Subash Abhinov Kasiviswanathan To: Dan Williams Cc: Alex Elder , Arnd Bergmann , David Miller , Bjorn Andersson , Ilias Apalodimas , evgreen@chromium.org, Ben Chan , Eric Caruso , cpratapa@codeaurora.org, syadagir@codeaurora.org, abhishek.esse@gmail.com, Networking , DTML , Linux Kernel Mailing List , linux-soc@vger.kernel.org, Linux ARM , linux-arm-msm@vger.kernel.org Subject: Re: [PATCH v2 00/17] net: introduce Qualcomm IPA driver In-Reply-To: <0fc29577a5c69530145b6095fa1ac1a51949ba8e.camel@redhat.com> References: <20190531035348.7194-1-elder@linaro.org> <065c95a8-7b17-495d-f225-36c46faccdd7@linaro.org> <3b1e12b145a273dd3ded2864d976bdc5fa90e68a.camel@redhat.com> <87f98f81-8f77-3bc5-374c-f498e07cb1bd@linaro.org> <0fc29577a5c69530145b6095fa1ac1a51949ba8e.camel@redhat.com> Message-ID: X-Sender: subashab@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org >> I can't (or won't) comment right now on whether IPA needs its own >> netdev for rmnet to use. The IPA endpoints used for the modem >> network interfaces are enabled when the netdev is opened and >> disabled when closed. Outside of that, TX and RX are pretty >> much immediately passed through to the layer below or above. >> IPA currently has no other net device operations. > > I don't really have issues with the patchset underneath the netdev > layer. I'm interested in how the various bits present themselves to > userspace, which is why I am trying to tie this in with Johannes' > conversation about WWAN devices, netdevs, channels, and how the various > drivers present API for creating data channels that map to different > modem contexts. > > So let me rephrase. If the control plane has set up the default context > and sent a QMI Start Network message (or the network attached the > default one) and the resulting IP details are applied to the IPA netdev > can things just start sending data? Or do we need to create an rmnet on > top to get that working? > > Dan Hi Dan All data from the hardware will have the MAP headers. We still need to create rmnet devs over the IPA netdev and use it for the data path. The IPA netdev will pass on the packets which it receives from the hardware and queue it to network stack where it will be intercepted by the rmnet rx handler. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project