archive mirror
 help / color / mirror / Atom feed
From: Aleksander Morgado <>
To: Stephan Gerhold <>
Cc: "David S. Miller" <>,
	Jakub Kicinski <>,
	Loic Poulain <>,
	Bjorn Andersson <>,
	Sergey Ryazanov <>,
	Johannes Berg <>,
	Leon Romanovsky <>,
	M Chetan Kumar <>,, Ohad Ben-Cohen <>,
	Mathieu Poirier <>,
	Network Development <>,,
	linux-arm-msm <>,,
	open list <>,
Subject: Re: [PATCH net-next v2 2/3] net: wwan: Add RPMSG WWAN CTRL driver
Date: Fri, 18 Jun 2021 10:21:18 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hey Stephan,

> +static const struct rpmsg_device_id rpmsg_wwan_ctrl_id_table[] = {
> +       /* RPMSG channels for Qualcomm SoCs with integrated modem */
> +       { .name = "DATA5_CNTL", .driver_data = WWAN_PORT_QMI },
> +       { .name = "DATA4", .driver_data = WWAN_PORT_AT },
> +       {},
> +};

If I understand this properly, now these rpmsg backed control ports
would be automatically exposed without the need of a userspace CLI
tool to do that (rpmsgexport).

And if I recall correctly, DATA5_CNTL and DATA4 were the only channels
actively exported with udev actions using rpmsgexport in postmarketos,
but that didn't mean someone could add additional rules to export
other channels (i.e. as per the ModemManager port type hint rules,
DATA[0-9]*_CNTL as QMI and DATA[0-9]* as AT, except for DATA40_CNTL
and DATA_40 which are the USB tethering related ones).

So, does this mean we're limiting the amount of channels exported to
only one QMI control port and one AT control port? Not saying that's
wrong, but maybe it makes sense to add a comment somewhere specifying
that explicitly.

Also, would it make sense to have some way to trigger the export of
additional channels somehow via userspace? e.g. something like
rpmsgexport but using the wwan subsystem. I'm not sure if that's a
true need anywhere or just over-engineering the solution, truth be


  reply	other threads:[~2021-06-18  8:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  7:52 [PATCH net-next v2 0/3] net: wwan: Add RPMSG WWAN CTRL driver Stephan Gerhold
2021-06-18  7:52 ` [PATCH net-next v2 1/3] rpmsg: core: Add driver_data for rpmsg_device_id Stephan Gerhold
2021-06-18  7:52 ` [PATCH net-next v2 2/3] net: wwan: Add RPMSG WWAN CTRL driver Stephan Gerhold
2021-06-18  8:21   ` Aleksander Morgado [this message]
2021-06-18 10:13     ` Stephan Gerhold
2021-06-18 12:24       ` Aleksander Morgado
2021-06-18  7:52 ` [PATCH net-next v2 3/3] net: wwan: Allow WWAN drivers to provide blocking tx and poll function Stephan Gerhold
2021-06-18 12:45   ` kernel test robot

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --cc=~postmarketos/ \

* 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).