netdev - Re: [PATCH net-next] net: wwan: iosm: Enable M.2 7360 WWAN card support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fb700c62-eca4-879b-1b1a-966d9232fd4d@linux.intel.com>
Date:   Thu, 10 Feb 2022 21:46:21 +0530
From:   "Kumar, M Chetan" <m.chetan.kumar@...ux.intel.com>
To:     Jan Kiszka <jan.kiszka@...mens.com>, netdev@...r.kernel.org
Cc:     kuba@...nel.org, davem@...emloft.net, johannes@...solutions.net,
        ryazanov.s.a@...il.com, loic.poulain@...aro.org,
        krishna.c.sudi@...el.com, linuxwwan@...el.com, flokli@...kli.de
Subject: Re: [PATCH net-next] net: wwan: iosm: Enable M.2 7360 WWAN card
 support

On 2/10/2022 9:08 PM, Jan Kiszka wrote:
> On 10.02.22 16:34, M Chetan Kumar wrote:
>> This patch enables Intel M.2 7360 WWAN card support on
>> IOSM Driver.
>>
>> Control path implementation is a reuse whereas data path
>> implementation it uses a different protocol called as MUX
>> Aggregation. The major portion of this patch covers the MUX
>> Aggregation protocol implementation used for IP traffic
>> communication.
>>
>> For M.2 7360 WWAN card, driver exposes 2 wwan AT ports for
>> control communication.  The user space application or the
>> modem manager to use wwan AT port for data path establishment.
>>
>> During probe, driver reads the mux protocol device capability
>> register to know the mux protocol version supported by device.
>> Base on which the right mux protocol is initialized for data
>> path communication.
>>
>> An overview of an Aggregation Protocol
>> 1>  An IP packet is encapsulated with 16 octet padding header
>>      to form a Datagram & the start offset of the Datagram is
>>      indexed into Datagram Header (DH).
>> 2>  Multiple such Datagrams are composed & the start offset of
>>      each DH is indexed into Datagram Table Header (DTH).
>> 3>  The Datagram Table (DT) is IP session specific & table_length
>>      item in DTH holds the number of composed datagram pertaining
>>      to that particular IP session.
>> 4>  And finally the offset of first DTH is indexed into DBH (Datagram
>>      Block Header).
>>
>> So in TX/RX flow Datagram Block (Datagram Block Header + Payload)is
>> exchanged between driver & device.
>>
>> Signed-off-by: M Chetan Kumar <m.chetan.kumar@...ux.intel.com>
> 
> Hey, cool! I'll be happy to try that out soon. Any special userland
> changes required, or will it "just work" with sufficiently recent
> ModemManager or whatever?

It need some changes at ModemManager side.