archive mirror
 help / color / mirror / Atom feed
From: Jeffrey Hugo <>
To: Hemant Kumar <>,,
Subject: Re: [PATCH v15 4/4] bus: mhi: Add userspace client interface driver
Date: Thu, 3 Dec 2020 16:45:24 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 12/3/2020 3:45 PM, Hemant Kumar wrote:
> This MHI client driver allows userspace clients to transfer
> raw data between MHI device and host using standard file operations.
> Driver instantiates UCI device object which is associated to device
> file node. UCI device object instantiates UCI channel object when device
> file node is opened. UCI channel object is used to manage MHI channels
> by calling MHI core APIs for read and write operations. MHI channels
> are started as part of device open(). MHI channels remain in start
> state until last release() is called on UCI device file node. Device
> file node is created with format
> /dev/<mhi_device_name>
> Currently it supports QMI channel.
> Signed-off-by: Hemant Kumar <>
> Reviewed-by: Manivannan Sadhasivam <>
> Reviewed-by: Jeffrey Hugo <>

You dropped Loic's tested by.  Was that a mistake, or did something 
actually change which would invalidate his testing?

Jeffrey Hugo
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.

  reply	other threads:[~2020-12-03 23:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 22:45 [PATCH v15 0/4] userspace MHI client interface driver Hemant Kumar
2020-12-03 22:45 ` [PATCH v15 1/4] bus: mhi: core: Add helper API to return number of free TREs Hemant Kumar
2020-12-03 22:45 ` [PATCH v15 2/4] bus: mhi: core: Move MHI_MAX_MTU to external header file Hemant Kumar
2020-12-03 22:45 ` [PATCH v15 3/4] docs: Add documentation for userspace client interface Hemant Kumar
2020-12-03 22:45 ` [PATCH v15 4/4] bus: mhi: Add userspace client interface driver Hemant Kumar
2020-12-03 23:45   ` Jeffrey Hugo [this message]
2020-12-04  2:31     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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).