From: "Kumar, M Chetan" <m.chetan.kumar@intel.com>
To: Aleksander Morgado <aleksander@aleksander.es>,
Loic Poulain <loic.poulain@linaro.org>
Cc: Network Development <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"Sudi, Krishna C" <krishna.c.sudi@intel.com>,
linuxwwan <linuxwwan@intel.com>
Subject: RE: [PATCH V2 00/16] net: iosm: PCIe Driver for Intel M.2 Modem
Date: Thu, 6 May 2021 10:51:12 +0000 [thread overview]
Message-ID: <2d2d9b2b138c454db0481d1c65b54a70@intel.com> (raw)
In-Reply-To: <CAAP7ucLwXqvc8sNpm8NtowFnKxcWKAwqwJEE89s9eME1YgCowQ@mail.gmail.com>
Hi Aleksander,
> > The IOSM (IPC over Shared Memory) driver is a PCIe host driver
> > implemented for linux or chrome platform for data exchange over PCIe
> > interface between Host platform & Intel M.2 Modem. The driver exposes
> > interface conforming to the MBIM protocol. Any front end application (
> > eg: Modem Manager) could easily manage the MBIM interface to enable
> data communication towards WWAN.
> >
> > Intel M.2 modem uses 2 BAR regions. The first region is dedicated to
> > Doorbell register for IRQs and the second region is used as scratchpad
> > area for book keeping modem execution stage details along with host
> > system shared memory region context details. The upper edge of the
> > driver exposes the control and data channels for user space
> > application interaction. At lower edge these data and control channels
> > are associated to pipes. The pipes are lowest level interfaces used
> > over PCIe as a logical channel for message exchange. A single channel maps
> to UL and DL pipe and are initialized on device open.
> >
> > On UL path, driver copies application sent data to SKBs associate it
> > with transfer descriptor and puts it on to ring buffer for DMA
> > transfer. Once information has been updated in shared memory region,
> > host gives a Doorbell to modem to perform DMA and modem uses MSI to
> communicate back to host.
> > For receiving data in DL path, SKBs are pre-allocated during pipe open
> > and transfer descriptors are given to modem for DMA transfer.
> >
> > The driver exposes two types of ports, namely "wwanctrl", a char
> > device node which is used for MBIM control operation and "INMx",(x =
> > 0,1,2..7) network interfaces for IP data communication.
>
> Is there any plan to integrate this driver in the new "wwan" subsystem so
> that the character device for MBIM control is exposed in the same format
> (i.e. same name rules and such) as with the MHI driver?
>
Yes, we are working on it. The next version of driver would have these adaptation to expose MBIM "WWAN Port".
Regards,
Chetan
prev parent reply other threads:[~2021-05-06 10:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 16:12 [PATCH V2 00/16] net: iosm: PCIe Driver for Intel M.2 Modem M Chetan Kumar
2021-04-20 16:12 ` [PATCH V2 01/16] net: iosm: entry point M Chetan Kumar
2021-04-21 5:44 ` Leon Romanovsky
2021-04-21 6:51 ` Johannes Berg
2021-04-21 8:03 ` Leon Romanovsky
2021-04-20 16:12 ` [PATCH V2 02/16] net: iosm: irq handling M Chetan Kumar
2021-04-20 23:48 ` David Miller
2021-04-20 16:12 ` [PATCH V2 03/16] net: iosm: mmio scratchpad M Chetan Kumar
2021-04-20 16:12 ` [PATCH V2 04/16] net: iosm: shared memory IPC interface M Chetan Kumar
2021-04-20 16:12 ` [PATCH V2 05/16] net: iosm: shared memory I/O operations M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 06/16] net: iosm: channel configuration M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 07/16] net: iosm: mbim control device M Chetan Kumar
2021-05-06 9:25 ` Loic Poulain
2021-05-06 10:44 ` Kumar, M Chetan
2021-05-06 14:09 ` Dan Williams
2021-04-20 16:13 ` [PATCH V2 08/16] net: iosm: bottom half M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 09/16] net: iosm: multiplex IP sessions M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 10/16] net: iosm: encode or decode datagram M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 11/16] net: iosm: power management M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 12/16] net: iosm: shared memory protocol M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 13/16] net: iosm: protocol operations M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 14/16] net: iosm: uevent support M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 15/16] net: iosm: net driver M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 16/16] net: iosm: infrastructure M Chetan Kumar
2021-04-20 18:08 ` Randy Dunlap
2021-05-06 8:54 ` [PATCH V2 00/16] net: iosm: PCIe Driver for Intel M.2 Modem Aleksander Morgado
2021-05-06 10:51 ` Kumar, M Chetan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d2d9b2b138c454db0481d1c65b54a70@intel.com \
--to=m.chetan.kumar@intel.com \
--cc=aleksander@aleksander.es \
--cc=johannes@sipsolutions.net \
--cc=krishna.c.sudi@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).