From: Hemant Kumar <hemantk@codeaurora.org>
To: Jeffrey Hugo <jhugo@codeaurora.org>,
Dan Williams <dcbw@redhat.com>, Jakub Kicinski <kuba@kernel.org>
Cc: 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
Subject: Re: [PATCH v9 3/4] docs: Add documentation for userspace client interface
Date: Mon, 26 Oct 2020 15:36:45 -0700 [thread overview]
Message-ID: <a0920f91-e043-8a67-f5c4-ea06eb1ddb2a@codeaurora.org> (raw)
In-Reply-To: <7934e50d-72bd-f20a-54da-33f29c66c3fa@codeaurora.org>
On 10/26/20 6:56 AM, Jeffrey Hugo wrote:
> On 10/26/2020 7:46 AM, Dan Williams wrote:
>> On Mon, 2020-10-26 at 07:38 -0600, Jeffrey Hugo wrote:
>>> 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).
>>
>> QMI too?
>> Dan
>
> Interesting question. My product doesn't use QMI. I would expect that
> all QMI runs through Router these days, but I am seeing some QMI
> channels in the downstream source.
>
> Hemant, Do you know what is the usecase for the QMI0/QMI1 channels?
>
QMI0/QMI1 is used to send QMI message (control path) to bring the qmi
rmnet data call.
Thanks,
Hemant
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2020-10-26 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 23:17 [PATCH v9 0/4] userspace MHI client interface driver Hemant Kumar
2020-10-23 23:17 ` [PATCH v9 1/4] bus: mhi: core: Add helper API to return number of free TREs Hemant Kumar
2020-10-23 23:17 ` [PATCH v9 2/4] bus: mhi: core: Move MHI_MAX_MTU to external header file Hemant Kumar
2020-10-23 23:17 ` [PATCH v9 3/4] docs: Add documentation for userspace client interface Hemant Kumar
2020-10-25 21:46 ` Jakub Kicinski
2020-10-26 13:38 ` Jeffrey Hugo
2020-10-26 13:46 ` Dan Williams
2020-10-26 13:56 ` Jeffrey Hugo
2020-10-26 22:36 ` Hemant Kumar [this message]
2020-10-26 22:56 ` Jakub Kicinski
2020-10-26 23:22 ` Hemant Kumar
2020-10-23 23:17 ` [PATCH v9 4/4] bus: mhi: Add userspace client interface driver Hemant Kumar
[not found] ` <CAMZdPi_MQ0SqK7s6h_1_9yEDD0vuAOpCTjSHTd1PBsGjvXukiA@mail.gmail.com>
2020-10-27 1:18 ` Hemant Kumar
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=a0920f91-e043-8a67-f5c4-ea06eb1ddb2a@codeaurora.org \
--to=hemantk@codeaurora.org \
--cc=bbhatt@codeaurora.org \
--cc=dcbw@redhat.com \
--cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).