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=-1.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, T_DKIMWL_WL_HIGH,URIBL_BLOCKED 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 9C97CC04AB5 for ; Mon, 3 Jun 2019 19:04:51 +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 706EA26FD5 for ; Mon, 3 Jun 2019 19:04:51 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="XQu+gEoy"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="aSz/Nurb"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="MoQ3CkC5" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 706EA26FD5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=codeaurora.org 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-Type: Content-Transfer-Encoding:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:Message-ID:References:In-Reply-To:Subject:To:From: Date:MIME-Version:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=YT7jYeEm1I736uJIdozCZl1wmVTmnjnISx240i7/rP0=; b=XQu+gEoyXNqfZ5OxASRYYTBhD EkjCEZte0NooHdCVd1JKK/nYNfJyXWF/r3Jqrl8FcogHqoN5WZPQxDrVrEQgvK/XP7H0ya/nqZnIy 9lcWAXElefIPnUXrfXHQG/hZPqIvFnqjgylPWLwKlkjkiMCEPmbTZci2PVBS7CcxarGrNoZZgI0Zm XvKTVMQOnL+EtGPKNJKDJPtNBmbiu62GStUXuy5SSUxX7bkaMbYOXNQ6REhzg+kf18UO9rwghuCZ3 HI9PqEKBPQE7CW0ONOZJsp0iGzgE9uOd2eSAi2UIse+M4DTD3MEX5cVk/IXq7nUeDt1FHg0gFbgKK BfHjXQxXQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hXsGE-0003Qo-Qn; Mon, 03 Jun 2019 19:04:46 +0000 Received: from smtp.codeaurora.org ([198.145.29.96]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hXsGC-0003PP-1d for linux-arm-kernel@lists.infradead.org; Mon, 03 Jun 2019 19:04:45 +0000 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 39BD160EA5; 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=1559588682; bh=2fFF2UZ1IMZoss2BdlfTKftG1dBbtIAex7bZx7hQCNA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=aSz/NurbMyqeUH2T7AzFoOZ/xsmW4Bf/FkDo33lpjwoR/+VFHCg6wSsM+iizRvLSh 8a/N7/vJ1OSK9AWz2nfz2fHYefLlH8t5pztgjCj5u1JUbc8HNAmrQNhmHdBjuFGbVt 316WuMJOnLtMatSgVgj+l47uQYdWAVwH5UsqFr9g= 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 Date: Mon, 03 Jun 2019 13:04:37 -0600 From: Subash Abhinov Kasiviswanathan To: Dan Williams 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 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190603_120444_132068_F1D57421 X-CRM114-Status: GOOD ( 14.45 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: DTML , syadagir@codeaurora.org, Eric Caruso , Arnd Bergmann , Networking , linux-arm-msm@vger.kernel.org, Ilias Apalodimas , Linux Kernel Mailing List , evgreen@chromium.org, Bjorn Andersson , abhishek.esse@gmail.com, Linux ARM , Alex Elder , linux-soc@vger.kernel.org, David Miller , cpratapa@codeaurora.org, Ben Chan Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.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 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel