From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jeffrey Hugo <jhugo@codeaurora.org>,
Hemant Kumar <hemantk@codeaurora.org>,
gregkh@linuxfoundation.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, bbhatt@codeaurora.org,
loic.poulain@linaro.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [PATCH v13 0/4] userspace MHI client interface driver
Date: Wed, 2 Dec 2020 09:45:59 +0530 [thread overview]
Message-ID: <20201202041559.GA3241@thinkpad> (raw)
In-Reply-To: <20201201120302.474d4c9b@kicinski-fedora-pc1c0hjn.DHCP.thefacebook.com>
On Tue, Dec 01, 2020 at 12:03:02PM -0800, Jakub Kicinski wrote:
> On Tue, 1 Dec 2020 12:40:50 -0700 Jeffrey Hugo wrote:
> > On 12/1/2020 12:29 PM, Jakub Kicinski wrote:
> > > On Fri, 27 Nov 2020 19:26:02 -0800 Hemant Kumar wrote:
> > >> This patch series adds support for UCI driver. UCI driver enables userspace
> > >> clients to communicate to external MHI devices like modem and WLAN. UCI driver
> > >> probe creates standard character device file nodes for userspace clients to
> > >> perform open, read, write, poll and release file operations. These file
> > >> operations call MHI core layer APIs to perform data transfer using MHI bus
> > >> to communicate with MHI device. Patch is tested using arm64 based platform.
> > >
> > > Wait, I thought this was for modems.
> > >
> > > Why do WLAN devices need to communicate with user space?
> > >
> >
> > Why does it matter what type of device it is? Are modems somehow unique
> > in that they are the only type of device that userspace is allowed to
> > interact with?
>
> Yes modems are traditionally highly weird and require some serial
> device dance I don't even know about.
>
> We have proper interfaces in Linux for configuring WiFi which work
> across vendors. Having char device access to WiFi would be a step
> back.
>
This is not for configuring the WiFi. This driver is mostly used for modems and
the AI accelerator Jeff is working on. But there might be a usecase for WLAN
devices as well to collect crash dumps and download fw (typical vendor ways) but
having those features are add-ons IMO.
So I think we should not be blocked by those usecases.
Thanks,
Mani
next prev parent reply other threads:[~2020-12-02 4:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 3:26 [PATCH v13 0/4] userspace MHI client interface driver Hemant Kumar
2020-11-28 3:26 ` [PATCH v13 1/4] bus: mhi: core: Add helper API to return number of free TREs Hemant Kumar
2020-11-28 3:26 ` [PATCH v13 2/4] bus: mhi: core: Move MHI_MAX_MTU to external header file Hemant Kumar
2020-11-28 3:26 ` [PATCH v13 3/4] docs: Add documentation for userspace client interface Hemant Kumar
2020-11-28 3:26 ` [PATCH v13 4/4] bus: mhi: Add userspace client interface driver Hemant Kumar
2020-11-28 6:11 ` Manivannan Sadhasivam
2020-12-01 1:08 ` Hemant Kumar
2020-11-30 18:22 ` Loic Poulain
2020-12-01 1:16 ` Hemant Kumar
2020-12-01 17:36 ` Loic Poulain
2020-12-01 17:37 ` Jeffrey Hugo
2020-12-01 17:52 ` Loic Poulain
2020-12-01 17:51 ` Jeffrey Hugo
2020-12-01 18:05 ` Loic Poulain
2020-12-01 18:04 ` Jeffrey Hugo
2020-12-01 21:59 ` Hemant Kumar
2020-12-01 19:29 ` [PATCH v13 0/4] userspace MHI " Jakub Kicinski
2020-12-01 19:40 ` Jeffrey Hugo
2020-12-01 20:03 ` Jakub Kicinski
2020-12-01 20:48 ` Jeffrey Hugo
2020-12-02 2:55 ` Jakub Kicinski
2020-12-02 4:59 ` Jeffrey Hugo
2020-12-06 8:33 ` Leon Romanovsky
2020-12-08 16:59 ` Manivannan Sadhasivam
2020-12-08 19:16 ` Leon Romanovsky
2020-12-02 4:15 ` Manivannan Sadhasivam [this message]
2020-12-02 4:38 ` Bjorn Andersson
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=20201202041559.GA3241@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bbhatt@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@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;
as well as URLs for NNTP newsgroup(s).