All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Poulain <loic.poulain@linaro.org>
To: Bhaumik Bhatt <bbhatt@codeaurora.org>
Cc: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	"Hemant Kumar" <hemantk@codeaurora.org>,
	"Jeffrey Hugo" <jhugo@codeaurora.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"Carl Yin(殷张成)" <carl.yin@quectel.com>,
	"Naveen Kumar" <naveen.kumar@quectel.com>
Subject: Re: [PATCH] bus: mhi: pci_generic: Apply no-op for wake using inband wake support flag
Date: Thu, 17 Jun 2021 20:52:26 +0200	[thread overview]
Message-ID: <CAMZdPi-r5CiuPT9vR+Pt3Q0nvy31m_NXW7fb7yJ3jPBSQBVH9A@mail.gmail.com> (raw)
In-Reply-To: <1623954233-32092-1-git-send-email-bbhatt@codeaurora.org>

On Thu, 17 Jun 2021 at 20:24, Bhaumik Bhatt <bbhatt@codeaurora.org> wrote:
>
> Devices such as SDX24 do not have the provision for inband wake
> doorbell in the form of channel 127. Newer devices such as SDX55
> or SDX65 have it by default. Ensure the functionality is used
> based on this such that device wake stays held when a client
> driver uses mhi_device_get() API or the equivalent debugfs entry.
>
> Fixes: e3e5e6508fc1 ("bus: mhi: pci_generic: No-Op for device_wake operations")
> Signed-off-by: Bhaumik Bhatt <bbhatt@codeaurora.org>

Reviewed-by: Loic Poulain <loic.poulain@linaro.org>

  reply	other threads:[~2021-06-17 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 18:23 [PATCH] bus: mhi: pci_generic: Apply no-op for wake using inband wake support flag Bhaumik Bhatt
2021-06-17 18:52 ` Loic Poulain [this message]
2021-06-17 21:58 ` Hemant Kumar
2021-06-18  6:52 ` Manivannan Sadhasivam
2021-06-18 17:06   ` Bhaumik Bhatt
2021-06-18 17:27     ` Manivannan Sadhasivam
2021-06-18 17:41       ` 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:
  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=CAMZdPi-r5CiuPT9vR+Pt3Q0nvy31m_NXW7fb7yJ3jPBSQBVH9A@mail.gmail.com \
    --to=loic.poulain@linaro.org \
    --cc=bbhatt@codeaurora.org \
    --cc=carl.yin@quectel.com \
    --cc=hemantk@codeaurora.org \
    --cc=jhugo@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=naveen.kumar@quectel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.