Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp314479pxt; Fri, 6 Aug 2021 02:44:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwZYF6PHMkJFETLlNk0iOMn3prpRygqEVE8whs0WXr8SBo6hAfnDhPzeHhIkmOum/m86y6h X-Received: by 2002:a5e:8402:: with SMTP id h2mr223191ioj.46.1628243061255; Fri, 06 Aug 2021 02:44:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628243061; cv=none; d=google.com; s=arc-20160816; b=U6TUshJ7KHFno3d39Mb73MIsczW/T5OsIlYugDQdF/qs2QW9jHvDvKMp7kJwnb+q00 +lfw9Chj9a95Kqb5EVYFxgdGAnUUQg17ytYlRJr10zqURAfgOqcRXtx3kfWOUnOmrEbK f02eJNc5ajpvKWOylEgVVnDZrkTWtP+sJV+8mm8Wy9s+v2aG4tkfSK+E6WlmRASae/Ij Pl87ShVkHF2HsEmivFmkH5bjXbx2fJb96tbSJibZ2905hYZZBd2ScWvLhU9CJYPX4qUt +iwG6S7ZGFAzOnpyjKUAhG23n71WjnznmKlbyVEW082k1p63PpUlMc0KFLdelTzhy8fw 34Cg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=WH/c1YD7AWRbi6CtkgPagHP/7bPfl6xTO6CIt3s1eGY=; b=aCg99B27nu9+zNcWhZ5ZMntgL2kctzVHIdgnHlG56+p8BtW9pqBo8GNGQvdT8cbBHc OIcMqd8LGgms3psPlmRwPn733Am+CUDGISKIS/B7RP7Nd3Mq4iW57v3QC17K/GDT11Vz s//hXQz9j83XD6/Wtz3uRpAGx6+d+nSHTBTsLbxFEh6q6juRIqE+mGUTjHZhgAePZscf 5lI5sIo8W1d3YI77C9an94PlimS8UgvEFbc302N1ZTAl3PMwoYBcrRadr8xPAVhLVZTA AeJHiHOxpsim7la1x4pzfVPuKi2UT5QoR7t8BrDiduaoS9awGB9BmHyZ0zqvQwh0MLe7 t7gg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d5si5873017jak.108.2021.08.06.02.44.10; Fri, 06 Aug 2021 02:44:21 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244612AbhHFJlv (ORCPT + 99 others); Fri, 6 Aug 2021 05:41:51 -0400 Received: from goliath.siemens.de ([192.35.17.28]:59925 "EHLO goliath.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242840AbhHFJlv (ORCPT ); Fri, 6 Aug 2021 05:41:51 -0400 Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id 1769fSDa026920 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 6 Aug 2021 11:41:28 +0200 Received: from [167.87.32.106] ([167.87.32.106]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 1769fRiq032085; Fri, 6 Aug 2021 11:41:28 +0200 Subject: Re: wwan/iosm vs. xmm7360 To: "Kumar, M Chetan" Cc: Linux Kernel Mailing List , Linux Netdev List , linuxwwan@intel.com References: <0545a78f-63f0-f8dd-abdb-1887c65e1c79@siemens.com> From: Jan Kiszka Message-ID: Date: Fri, 6 Aug 2021 11:41:27 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06.08.21 11:29, Kumar, M Chetan wrote: > Hi Jan, > > What is the context of this request ? The context is that there are many folks out there (me included - Lenovo P52) with devices that have the xmm-7360 built-in, can't switch it to USB mode (prevented by OEM), and currently require [1]. That kind of works but is not really the final solution. So I also kicked off [2] there. > > FYI, the driver upstreamed is for M.2 7560. I know. I'm not an expert on the details, but reading the overall architectures of the IOSM and what has been reverse-engineered for the 7360, there seem to be some similarities. So, maybe you can explain to the community if that is a reasonable path to upstream 7360 support, or if at least the pattern of the 7560 could/should be transferred to the 7360 driver. Thanks, Jan [2] https://github.com/xmm7360/xmm7360-pci/issues/104 > > Regards, > Chetan > > On 8/6/2021 2:09 AM, Jan Kiszka wrote: >> Hi Chetan, >> >> at the risk of having missed this being answered already: >> >> How close is the older xmm7360 to the now supported xmm7560 in mainline? >> >> There is that reverse engineered PCI driver [1] with non-standard >> userland interface, and it would obviously be great to benefit from >> common infrastructure and specifically the modem-manager compatible >> interface. Is this realistic to achieve for the 7360, or is that >> hardware or its firmware too different? >> >> Thanks, >> Jan >> >> [1] https://github.com/xmm7360/xmm7360-pci >> -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux