[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e92a5a5b-ac62-a6d8-b6b4-b65587e64255@codeaurora.org>
Date: Mon, 26 Oct 2020 07:38:46 -0600
From: Jeffrey Hugo <jhugo@...eaurora.org>
To: Jakub Kicinski <kuba@...nel.org>,
Hemant Kumar <hemantk@...eaurora.org>
Cc: manivannan.sadhasivam@...aro.org, gregkh@...uxfoundation.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
bbhatt@...eaurora.org, loic.poulain@...aro.org,
netdev@...r.kernel.org
Subject: Re: [PATCH v9 3/4] docs: Add documentation for userspace client
interface
On 10/25/2020 3:46 PM, Jakub Kicinski wrote:
> On Fri, 23 Oct 2020 16:17:54 -0700 Hemant Kumar wrote:
>> +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.
>
> What's the user space that talks to this?
>
Multiple.
Each channel has a different purpose. There it is expected that a
different userspace application would be using it.
Hemant implemented the loopback channel, which is a simple channel that
just sends you back anything you send it. Typically this is consumed by
a test application.
Diag is a typical channel to be consumed by userspace. This is consumed
by various applications that talk to the remote device for diagnostic
information (logs and such).
Sahara is another common channel that is usually used for the multistage
firmware loading process.
--
Jeffrey Hugo
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
Powered by blists - more mailing lists