From: Jeffrey Hugo <jhugo@codeaurora.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Hemant Kumar <hemantk@codeaurora.org>,
manivannan.sadhasivam@linaro.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: Tue, 1 Dec 2020 13:48:36 -0700 [thread overview]
Message-ID: <817a4346-efb7-cfe5-0678-d1b60d06627d@codeaurora.org> (raw)
In-Reply-To: <20201201120302.474d4c9b@kicinski-fedora-pc1c0hjn.DHCP.thefacebook.com>
On 12/1/2020 1:03 PM, 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.
So a WLAN device is only ever allowed to do Wi-Fi? It can't also have
GPS functionality for example?
>
>> However, I'll bite. Once such usecase would be QMI. QMI is a generic
>> messaging protocol, and is not strictly limited to the unique operations
>> of a modem.
>>
>> Another usecase would be Sahara - a custom file transfer protocol used
>> for uploading firmware images, and downloading crashdumps.
>
> Thanks, I was asking for use cases, not which proprietary vendor
> protocol you can implement over it.
>
> None of the use cases you mention here should require a direct FW -
> user space backdoor for WLAN.
Uploading runtime firmware, with variations based on the runtime mode.
Flashing the onboard flash based on cryptographic keys. Accessing
configuration data. Accessing device logs. Configuring device logs.
Synchronizing the device time reference to Linux local or remote time
sources. Enabling debugging/performance hardware. Getting software
diagnostic events. Configuring redundancy hardware per workload.
Uploading new cryptographic keys. Invalidating cryptographic keys.
Uploading factory test data and running factory tests.
Need more?
--
Jeffrey Hugo
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2020-12-01 20:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 3:26 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 [this message]
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
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=817a4346-efb7-cfe5-0678-d1b60d06627d@codeaurora.org \
--to=jhugo@codeaurora.org \
--cc=bbhatt@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@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=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
Powered by JetHome