On Fri, Jul 24, 2020 at 04:47:44PM -0700, Hemant Kumar wrote:
> Hi Mani,
>
> On 7/22/20 1:45 AM, Manivannan Sadhasivam wrote:
> > On Mon, Jul 20, 2020 at 08:40:24PM -0700, Hemant Kumar wrote:
> > > Hi Mani,
> > >
> > > On 6/19/20 3:40 AM, Manivannan Sadhasivam wrote:
> > > > On Thu, Jun 11, 2020
Hi Mani,
On 7/22/20 1:45 AM, Manivannan Sadhasivam wrote:
On Mon, Jul 20, 2020 at 08:40:24PM -0700, Hemant Kumar wrote:
Hi Mani,
On 6/19/20 3:40 AM, Manivannan Sadhasivam wrote:
On Thu, Jun 11, 2020 at 11:13:44AM -0700, Hemant Kumar wrote:
This MHI client driver allows user space clients to
On Mon, Jul 20, 2020 at 08:40:24PM -0700, Hemant Kumar wrote:
> Hi Mani,
>
> On 6/19/20 3:40 AM, Manivannan Sadhasivam wrote:
> > On Thu, Jun 11, 2020 at 11:13:44AM -0700, Hemant Kumar wrote:
> > > This MHI client driver allows user space clients to transfer
> > > data between MHI device and host
Hi Mani,
On 6/19/20 3:40 AM, Manivannan Sadhasivam wrote:
On Thu, Jun 11, 2020 at 11:13:44AM -0700, Hemant Kumar wrote:
This MHI client driver allows user space clients to transfer
data between MHI device and host using standard file operations.
I think we need to explicitly specify 'raw'
On Thu, Jun 11, 2020 at 11:13:44AM -0700, Hemant Kumar wrote:
> This MHI client driver allows user space clients to transfer
> data between MHI device and host using standard file operations.
I think we need to explicitly specify 'raw' data here. Because we have different
APIs for queuing
This MHI client driver allows user space clients to transfer
data between MHI device and host using standard file operations.
Device file node is created with format
/dev/mhi__
Currently it supports loopback client.
Signed-off-by: Hemant Kumar
---
drivers/bus/mhi/Kconfig | 2 +
6 matches
Mail list logo
