archive mirror
 help / color / mirror / Atom feed
From: Hemant Kumar <>
To: Bhaumik Bhatt <>,
Subject: Re: [PATCH v4 1/8] bus: mhi: core: Allow sending the STOP channel command
Date: Thu, 3 Dec 2020 19:44:48 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 12/3/20 5:23 PM, Bhaumik Bhatt wrote:
> Add support to allow sending the STOP channel command. If a
> client driver would like to STOP a channel and have the device
> retain the channel context instead of issuing a RESET to it and
> clearing the context, this would provide support for it after
> the ability to send this command is exposed to clients.
> Signed-off-by: Bhaumik Bhatt <>
> ---

Reviewed-by: Hemant Kumar <>
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2020-12-04  3:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  1:23 [PATCH v4 0/8] Updates to MHI channel handling Bhaumik Bhatt
2020-12-04  1:23 ` [PATCH v4 1/8] bus: mhi: core: Allow sending the STOP channel command Bhaumik Bhatt
2020-12-04  3:44   ` Hemant Kumar [this message]
2020-12-04  1:23 ` [PATCH v4 2/8] bus: mhi: core: Allow channel to be disabled from stopped state Bhaumik Bhatt
2020-12-04  1:23 ` [PATCH v4 3/8] bus: mhi: core: Improvements to the channel handling state machine Bhaumik Bhatt
2020-12-04  1:23 ` [PATCH v4 4/8] bus: mhi: core: Clear configuration from channel context during reset Bhaumik Bhatt
2020-12-04  3:49   ` Hemant Kumar
2020-12-04  1:23 ` [PATCH v4 5/8] bus: mhi: core: Add support to stop or start channel data transfers Bhaumik Bhatt
2020-12-04  3:50   ` Hemant Kumar
2020-12-04  1:23 ` [PATCH v4 6/8] bus: mhi: core: Check channel execution environment before issuing reset Bhaumik Bhatt
2020-12-04  1:23 ` [PATCH v4 7/8] bus: mhi: core: Remove __ prefix for MHI channel unprepare function Bhaumik Bhatt
2020-12-04  1:23 ` [PATCH v4 8/8] bus: mhi: Improve documentation on channel transfer setup APIs Bhaumik Bhatt

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