From: Slark Xiao <slark_xiao@163.com>
To: loic.poulain@oss.qualcomm.com, ryazanov.s.a@gmail.com,
johannes@sipsolutions.net, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mani@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, slark_xiao@163.com
Subject: [net-next v6 0/8] net: wwan: add NMEA port type support
Date: Thu, 15 Jan 2026 17:54:09 +0800 [thread overview]
Message-ID: <20260115095417.36975-1-slark_xiao@163.com> (raw)
The series introduces a long discussed NMEA port type support for the
WWAN subsystem. There are two goals. From the WWAN driver perspective,
NMEA exported as any other port type (e.g. AT, MBIM, QMI, etc.). From
user space software perspective, the exported chardev belongs to the
GNSS class what makes it easy to distinguish desired port and the WWAN
device common to both NMEA and control (AT, MBIM, etc.) ports makes it
easy to locate a control port for the GNSS receiver activation.
Done by exporting the NMEA port via the GNSS subsystem with the WWAN
core acting as proxy between the WWAN modem driver and the GNSS
subsystem.
The series starts from a cleanup patch. Then three patches prepares the
WWAN core for the proxy style operation. Followed by a patch introding a
new WWNA port type, integration with the GNSS subsystem and demux. The
series ends with a couple of patches that introduce emulated EMEA port
to the WWAN HW simulator.
The series is the product of the discussion with Loic about the pros and
cons of possible models and implementation. Also Muhammad and Slark did
a great job defining the problem, sharing the code and pushing me to
finish the implementation. Daniele has caught an issue on driver
unloading and suggested an investigation direction. What was concluded
by Loic. Many thanks.
Changes RFCv1->RFCv2:
* Uniformly use put_device() to release port memory. This made code less
weird and way more clear. Thank you, Loic, for noticing and the fix
discussion!
Changes RFCv2->RFCv5:
* Fix premature WWAN device unregister; new patch 2/7, thus, all
subsequent patches have been renumbered
* Minor adjustments here and there
Sergey Ryazanov (7):
net: wwan: core: remove unused port_id field
net: wwan: core: explicit WWAN device reference counting
net: wwan: core: split port creation and registration
net: wwan: core: split port unregister and stop
net: wwan: add NMEA port support
net: wwan: hwsim: refactor to support more port types
net: wwan: hwsim: support NMEA port emulation
Slark Xiao (1):
net: wwan: mhi_wwan_ctrl: Add NMEA channel support
drivers/net/wwan/Kconfig | 1 +
drivers/net/wwan/mhi_wwan_ctrl.c | 1 +
drivers/net/wwan/wwan_core.c | 277 +++++++++++++++++++++++++------
drivers/net/wwan/wwan_hwsim.c | 201 ++++++++++++++++++----
include/linux/wwan.h | 2 +
5 files changed, 394 insertions(+), 88 deletions(-)
--
2.25.1
next reply other threads:[~2026-01-15 9:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 9:54 Slark Xiao [this message]
2026-01-15 9:54 ` [net-next v6 1/8] net: wwan: core: remove unused port_id field Slark Xiao
2026-01-15 9:54 ` [net-next v6 2/8] net: wwan: core: explicit WWAN device reference counting Slark Xiao
2026-01-15 9:54 ` [net-next v6 3/8] net: wwan: core: split port creation and registration Slark Xiao
2026-01-15 9:54 ` [net-next v6 4/8] net: wwan: core: split port unregister and stop Slark Xiao
2026-01-15 9:54 ` [net-next v6 5/8] net: wwan: add NMEA port support Slark Xiao
2026-01-15 9:54 ` [net-next v6 6/8] net: wwan: hwsim: refactor to support more port types Slark Xiao
2026-01-15 9:54 ` [net-next v6 7/8] net: wwan: hwsim: support NMEA port emulation Slark Xiao
2026-01-15 9:54 ` [net-next v6 8/8] net: wwan: mhi_wwan_ctrl: Add NMEA channel support Slark Xiao
2026-01-15 11:43 ` Re:[net-next v6 0/8] net: wwan: add NMEA port type support Slark Xiao
2026-01-16 2:41 ` [net-next " Jakub Kicinski
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=20260115095417.36975-1-slark_xiao@163.com \
--to=slark_xiao@163.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mani@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryazanov.s.a@gmail.com \
/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
all inboxes | Powered by JetHome®