From: Randy Dunlap <rdunlap@infradead.org>
To: Loic Poulain <loic.poulain@linaro.org>,
kuba@kernel.org, davem@davemloft.net, gregkh@linuxfoundation.org
Cc: linux-arm-msm@vger.kernel.org, aleksander@aleksander.es,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bjorn.andersson@linaro.org, manivannan.sadhasivam@linaro.org,
hemantk@codeaurora.org, jhugo@codeaurora.org
Subject: Re: [PATCH net-next v4 2/2] net: Add Qcom WWAN control driver
Date: Thu, 11 Mar 2021 10:58:11 -0800 [thread overview]
Message-ID: <bb73e0bf-1c30-89f7-a28d-4e51998eec9f@infradead.org> (raw)
In-Reply-To: <1615480746-28518-2-git-send-email-loic.poulain@linaro.org>
On 3/11/21 8:39 AM, Loic Poulain wrote:
> diff --git a/drivers/net/wwan/Kconfig b/drivers/net/wwan/Kconfig
> index b7d58b7..1e8ac0b 100644
> --- a/drivers/net/wwan/Kconfig
> +++ b/drivers/net/wwan/Kconfig
> @@ -16,4 +16,18 @@ config WWAN_CORE
> Say Y here if you want to use the WWAN driver core. This driver
> provides a common framework for WWAN drivers.
>
> +config MHI_WWAN_CTRL
> + tristate "MHI WWAN control driver for QCOM based PCIe modems"
QCOM-based
> + select WWAN_CORE
> + depends on MHI_BUS
> + help
> + MHI WWAN CTRL allow QCOM based PCIe modems to expose different modem
allows QCOM-based
> + control protocols/ports to userspace, including AT, MBIM, QMI, DIAG
> + and FIREHOSE. These protocols can be accessed directly from userspace
> + (e.g. AT commands) or via libraries/tools (e.g. libmbim, libqmi,
> + libqcdm...).
> +
> + To compile this driver as a module, choose M here: the module will be
> + called mhi_wwan_ctrl.
> +
> endif # WWAN
--
~Randy
next prev parent reply other threads:[~2021-03-11 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 16:39 [PATCH net-next v4 1/2] net: Add a WWAN subsystem Loic Poulain
2021-03-11 16:39 ` [PATCH net-next v4 2/2] net: Add Qcom WWAN control driver Loic Poulain
2021-03-11 18:58 ` Randy Dunlap [this message]
2021-03-11 16:48 ` [PATCH net-next v4 1/2] net: Add a WWAN subsystem Greg KH
2021-03-11 17:14 ` Loic Poulain
2021-03-11 16:48 ` Greg KH
2021-03-11 18:52 ` 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:
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=bb73e0bf-1c30-89f7-a28d-4e51998eec9f@infradead.org \
--to=rdunlap@infradead.org \
--cc=aleksander@aleksander.es \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@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