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=-3.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no 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 18F7EC433E9 for ; Sun, 28 Feb 2021 14:13:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CE9D064EBD for ; Sun, 28 Feb 2021 14:13:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230438AbhB1ONh (ORCPT ); Sun, 28 Feb 2021 09:13:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39160 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230139AbhB1ONe (ORCPT ); Sun, 28 Feb 2021 09:13:34 -0500 Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 185F7C061756 for ; Sun, 28 Feb 2021 06:12:54 -0800 (PST) Received: by mail-ot1-x32e.google.com with SMTP id g8so10275620otk.4 for ; Sun, 28 Feb 2021 06:12:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aleksander-es.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2FusiFiz0X86EPMHGdKHS7UxChtJqFIAQKwqNSegRJI=; b=kuqs/varyC0CfTq+gxGmOMXaztlbrXePfmB2FleBx3n1SkuYpluH3XMLBMedDMcVwk Cl5rTxhhuvWHLNZzL3vfsK0Xd+C0KaSRpJjjOVPGuyix0yYihLCUPxdXSi5ZyP5rg4mg F6xSBRYyIzLN1h86tEwNcTxuxTmKJXCiPcuA193BLmPBaZXC3EpJjHd1J4OWdKKOHtWY 7dsPqo4A56Ngd2y8mnyAknhr3nEgczxx736+mNJQMDTAh8JdgEjeOJG8tf1Uv/8gfC98 1k4uhctwtdIlpqZdXDKYuPFzwD5fVqvMbpAggN7clrIEf1593IqlbojZt1+ybWoDWT8+ YlQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2FusiFiz0X86EPMHGdKHS7UxChtJqFIAQKwqNSegRJI=; b=d1wq1g4+ENl0cUBw0HMKvGQG5nrknIBgvKKx2xsYxCIxDmKrvBrN/2jnVfe/EpfBUz 4zJv8hOVtR9RYkm/DDw84CnXh1FoHSiwPKRnV1TCfRWAIGkgBfBmbys+BB5TogVtZIXp 6atCJPcxxbbm2Vy5JUFFtKqGWAZEV2ufKeIZkjmvJHwCeXkQwaXs7kznWMtR1QI+awjZ N3TaVZvoeGmrZxy4vrUHb0oVLkBQzW0L9rRUHPpgCIt6gjKjpTyMN+pFRqUGCQtIgfZY K84BssnxTUg3eKPZzNn8VEBCdvvYLPTwc0lyN7RlnISYRqzE9maYheJ+6zbkhl1xDM5P XMsQ== X-Gm-Message-State: AOAM5332Ds3r3e0+9fuaBth14z3Mz4MBRzna3EifwP9K8ztNgLVobdpz PKMvBKfew+6g0EQFy5fWzX+fL3iINtA6G3qt4SOXlQ== X-Google-Smtp-Source: ABdhPJxbAVFinsYw6ljwDBh6vBidfD1MwQjl+p3XMISJMExPhTMIPnKo7bYd1V0jz5Nk4OkPPQe2y8BBJxvdyTKhAsc= X-Received: by 2002:a05:6830:151:: with SMTP id j17mr10155633otp.252.1614521573376; Sun, 28 Feb 2021 06:12:53 -0800 (PST) MIME-Version: 1.0 References: <20210201121322.GC108653@thinkpad> <20210202042208.GB840@work> <20210202201008.274209f9@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <835B2E08-7B84-4A02-B82F-445467D69083@linaro.org> <20210203100508.1082f73e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <20210203104028.62d41962@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <20210209081744.43eea7b5@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <20210210062531.GA13668@work> In-Reply-To: <20210210062531.GA13668@work> From: Aleksander Morgado Date: Sun, 28 Feb 2021 15:12:42 +0100 Message-ID: Subject: Re: [RESEND PATCH v18 0/3] userspace MHI client interface driver To: Manivannan Sadhasivam Cc: Jakub Kicinski , Loic Poulain , Greg KH , David Miller , linux-arm-msm , open list , Jeffrey Hugo , Bhaumik Bhatt , Network Development Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hey Manivannan, Jakub & all, > > So please let us know the path forward on this series. We are open to > any suggestions but you haven't provided one till now. > I just found out that Sierra Wireless also provides their own version of mhi-net and mhi-uci in precompiled binaries for several Ubuntu kernel versions and other setups; and that made me extremely unhappy. They're not the only manufacturer doing that; most of them are doing it, because we don't have yet a common solution in upstream Linux. Not the first time we've seen this either, see the per-vendor GobiNet implementations vs the upstream qmi_wwan one. I was hoping we could avoid that mess again with the newer Qualcomm modules! :) In ModemManager we've always *forced* all manufacturers we interact with to first do the work in upstream Linux, and then we integrate support in MM for those drivers. We've never accepted support for vendor-specific proprietary kernel drivers, and that's something I would personally like to keep on doing. The sad status right now is that any user that wants to use the newer 5G modules with Qualcomm chipsets, they need to go look for manufacturer-built precompiled drivers for their specific kernel, and also then patch ModemManager and the tools themselves. Obviously almost no one is doing all that, except for some company with resources or a lot of interest. Some of these new 5G modules are PCIe-only by default, unless some pin in the chipset is brought up and then some of them may switch to USB support. No one is really doing that either, as tampering with the hardware voids warranty. The iosm driver is also stalled in the mailing list and there doesn't seem to be a lot of real need for a new common wwan subsystem to rework everything... I'm not involved with the mhi-uci driver development at all, and I also don't have anything to say on what goes in the upstream kernel and what doesn't. But as one of the ModemManager/libqmi/libmbim maintainers I would like to represent all the users of these modules that are right now forced to look for shady binary precompiled drivers out there... that is no better solution than this proposed mhi-uci common driver. Manivannan, are you attempting to rework the mhi-uci driver in a different way, or have you given up? Is there anything I could help with? Jakub, is there really no way you can be convinced that this mhi-uci driver isn't that bad after all? :) All the mhi-net bits are already integrated I think, even the MBIM support over MHI in the net device, but all that is truly useless without a way to control the modem sending and receiving messages. Sorry for being back again with this discussion :) Cheers! -- Aleksander https://aleksander.es