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.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 535BCC4321A for ; Tue, 11 Jun 2019 16:52:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2783D21734 for ; Tue, 11 Jun 2019 16:52:21 +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="m2CioZUe"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="GVUgVMbH" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405418AbfFKQwV (ORCPT ); Tue, 11 Jun 2019 12:52:21 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:35092 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389757AbfFKQwU (ORCPT ); Tue, 11 Jun 2019 12:52:20 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 7EA8F60A44; Tue, 11 Jun 2019 16:52:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1560271938; bh=EWaGYlUEtSJujntfkWWkNzZfnY+gc4hFdn9MEawiOP4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=m2CioZUe39qanfZOhd2/d8dal/I3jVR8/l4r4reFyc8TdLHfBORMaDr9wqALUZid1 tXv4GBBedi4ZFLoniNZB84Jz3pJncerK1B8KHYBYPZ0lwqMJ2Pm6o+sdLcalqm5fda Jh5Mw12a9TpP1nz3RdfIl4YYyZs/3ttYhu6i+BJY= Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id 49EEC60271; Tue, 11 Jun 2019 16:52:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1560271937; bh=EWaGYlUEtSJujntfkWWkNzZfnY+gc4hFdn9MEawiOP4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=GVUgVMbHCn+CkS+MkbgWO1xjbxVXlrgAfcqcLDDPrYmv53U3DmsA9KqaY+VVMcCAX LbNUFiCHvOuzzsXWd0/6RoLBMJMwiGH8pqqtxv8asl/vqenfY07xMTVVUgyX7E4/FX qU+52UHW3jdR4ObZArHFdrEDpecgTRN8yqq634QI= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 11 Jun 2019 10:52:16 -0600 From: Subash Abhinov Kasiviswanathan To: Dan Williams Cc: Arnd Bergmann , Johannes Berg , Alex Elder , abhishek.esse@gmail.com, Ben Chan , Bjorn Andersson , cpratapa@codeaurora.org, David Miller , DTML , Eric Caruso , evgreen@chromium.org, Ilias Apalodimas , Linux ARM , linux-arm-msm@vger.kernel.org, Linux Kernel Mailing List , linux-soc@vger.kernel.org, Networking , syadagir@codeaurora.org Subject: Re: [PATCH v2 00/17] net: introduce Qualcomm IPA driver In-Reply-To: References: <380a6185-7ad1-6be0-060b-e6e5d4126917@linaro.org> Message-ID: <36bca57c999f611353fd9741c55bb2a7@codeaurora.org> X-Sender: subashab@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > The general plan (and I believe Daniele Palmas was working on it) was > to eventually make qmi_wwan use rmnet rather than its internal sysfs- > based implementation. qmi_wwan and ipa are at essentially the same > level and both could utilize rmnet on top. > > *That's* what I'd like to see. I don't want to see two different ways > to get QMAP packets to modem firmware from two different drivers that > really could use the same code. > > Dan qmi_wwan is based on USB and is very different from the IPA interconnect though. AFAIK, they do not have much in common (apart from sending & receiving MAP packets from hardware). -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project