All of lore.kernel.org
 help / color / mirror / Atom feed
From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
To: Daniele Palmas <dnlplm@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Qualcomm rmnet driver and qmi_wwan
Date: Wed, 21 Feb 2018 12:47:40 -0700	[thread overview]
Message-ID: <2a96c941b6699827ea6ac1ce3603fae5@codeaurora.org> (raw)
In-Reply-To: <CAGRyCJH2Jg_TQn2rneMgHRP69Qo0Rf0XMcGby9MsBuCjg8_ysw@mail.gmail.com>

On 2018-02-21 04:38, Daniele Palmas wrote:
> Hello,
> 
> in rmnet kernel documentation I read:
> 
> "This driver can be used to register onto any physical network device 
> in
> IP mode. Physical transports include USB, HSIC, PCIe and IP 
> accelerator."
> 
> Does this mean that it can be used in association with the qmi_wwan 
> driver?
> 
> If yes, can someone give me an hint on the steps to follow?
> 
> If not, does anyone know if it is possible to modify qmi_wwan in order
> to take advantage of the features provided by the rmnet driver?
> 
> In this case hint on the changes for modifying qmi_wwan are welcome.
> 
> Thanks in advance,
> Daniele

Hi

I havent used qmi_wwan so the following comment is based on code 
inspection.
qmimux_register_device() is creating qmimux devices with usb net device 
as
real_dev. The Multiplexing and aggregation header (qmimux_hdr) is 
stripped off
in qmimux_rx_fixup() and the packet is passed on to stack.

You could instead create rmnet devices with the usb netdevice as real 
dev.
The packets from the usb net driver can be queued to network stack 
directly
as rmnet driver will setup a RX handler. rmnet driver will process the 
packets
further and then queue to network stack.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2018-02-21 19:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 11:38 Qualcomm rmnet driver and qmi_wwan Daniele Palmas
2018-02-21 19:47 ` Subash Abhinov Kasiviswanathan [this message]
2018-02-22 10:44   ` Daniele Palmas
2018-06-05  9:38   ` Daniele Palmas
2018-06-05 14:54     ` Dan Williams
2018-06-05 17:38       ` Subash Abhinov Kasiviswanathan
2018-06-08 10:21         ` Daniele Palmas
2018-06-08 17:19           ` Subash Abhinov Kasiviswanathan
2018-06-08 19:10             ` Bjørn Mork
2018-06-09  2:19               ` Subash Abhinov Kasiviswanathan
2018-06-09  7:22                 ` Daniele Palmas
2018-06-09 17:55                   ` Subash Abhinov Kasiviswanathan
2018-06-11 14:30                     ` Daniele Palmas
2018-06-11 17:43                     ` Bjørn Mork
2018-06-11 23:00                       ` Subash Abhinov Kasiviswanathan

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=2a96c941b6699827ea6ac1ce3603fae5@codeaurora.org \
    --to=subashab@codeaurora.org \
    --cc=dnlplm@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.