From: Stephan Gerhold <stephan@gerhold.net>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Loic Poulain <loic.poulain@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Aleksander Morgado <aleksander@aleksander.es>,
Sergey Ryazanov <ryazanov.s.a@gmail.com>,
Johannes Berg <johannes.berg@intel.com>,
M Chetan Kumar <m.chetan.kumar@intel.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
netdev@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-arm-msm@vger.kernel.org, phone-devel@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Stephan Gerhold <stephan@gerhold.net>
Subject: [PATCH net-next 0/3] net: wwan: Add RPMSG WWAN CTRL driver
Date: Tue, 15 Jun 2021 15:32:26 +0200 [thread overview]
Message-ID: <20210615133229.213064-1-stephan@gerhold.net> (raw)
This patch series adds a WWAN "control" driver for the remote processor
messaging (rpmsg) subsystem. This subsystem allows communicating with
an integrated modem DSP on many Qualcomm SoCs, e.g. MSM8916 or MSM8974.
The driver is a fairly simple glue layer between WWAN and RPMSG
and is mostly based on the existing mhi_wwan_ctrl.c and rpmsg_char.c.
For more information, see commit message in PATCH 2/3.
I already posted a RFC for this a while ago:
https://lore.kernel.org/linux-arm-msm/YLfL9Q+4860uqS8f@gerhold.net/
and now I'm looking for some feedback for the actual changes. :)
Especially patch 3/3 is still up for discussion, perhaps there is a cleaner
way to implement the blocking/non-blocking writes for rpmsg_wwan_ctrl?
Stephan Gerhold (3):
rpmsg: core: Add driver_data for rpmsg_device_id
net: wwan: Add RPMSG WWAN CTRL driver
net: wwan: Allow WWAN drivers to provide blocking tx and poll function
MAINTAINERS | 7 ++
drivers/net/wwan/Kconfig | 18 +++
drivers/net/wwan/Makefile | 1 +
drivers/net/wwan/iosm/iosm_ipc_port.c | 3 +-
drivers/net/wwan/mhi_wwan_ctrl.c | 3 +-
drivers/net/wwan/rpmsg_wwan_ctrl.c | 156 ++++++++++++++++++++++++++
drivers/net/wwan/wwan_core.c | 9 +-
drivers/net/wwan/wwan_hwsim.c | 3 +-
drivers/rpmsg/rpmsg_core.c | 4 +-
include/linux/mod_devicetable.h | 1 +
include/linux/wwan.h | 13 ++-
11 files changed, 207 insertions(+), 11 deletions(-)
create mode 100644 drivers/net/wwan/rpmsg_wwan_ctrl.c
--
2.32.0
next reply other threads:[~2021-06-15 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 13:32 Stephan Gerhold [this message]
2021-06-15 13:32 ` [PATCH net-next 1/3] rpmsg: core: Add driver_data for rpmsg_device_id Stephan Gerhold
2021-06-15 13:32 ` [PATCH net-next 2/3] net: wwan: Add RPMSG WWAN CTRL driver Stephan Gerhold
2021-06-15 13:32 ` [PATCH net-next 3/3] net: wwan: Allow WWAN drivers to provide blocking tx and poll function Stephan Gerhold
2021-06-15 21:24 ` Loic Poulain
2021-06-15 22:06 ` Stephan Gerhold
2021-06-16 9:28 ` Loic Poulain
2021-06-16 17:13 ` Stephan Gerhold
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=20210615133229.213064-1-stephan@gerhold.net \
--to=stephan@gerhold.net \
--cc=aleksander@aleksander.es \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@intel.com \
--cc=mathieu.poirier@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=phone-devel@vger.kernel.org \
--cc=ryazanov.s.a@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).