From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
robh+dt@kernel.org, vkoul@kernel.org,
yung-chuan.liao@linux.intel.com
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, quic_srivasam@quicinc.com
Subject: Re: [PATCH v2 3/3] soundwire: qcom: add in-band wake up interrupt support
Date: Thu, 24 Feb 2022 09:44:23 -0600 [thread overview]
Message-ID: <87f434b5-0e99-d1d1-e4d1-248cf35cd05c@linux.intel.com> (raw)
In-Reply-To: <20220224133125.6674-4-srinivas.kandagatla@linaro.org>
On 2/24/22 07:31, Srinivas Kandagatla wrote:
> Some of the Qualcomm SoundWire Controller instances like the ones that are
> connected to RX path along with Headset connections support Waking up
> Controller from Low power clock stop state using SoundWire In-band interrupt.
> SoundWire Slave on the bus would intiate this by pulling the data line high,
typo: initiate
> during clock stop condition.
while the clock is stopped.
A peripheral cannot generate an interrupt after a successful completion
of a write to the ClockStopNow bitfield.
prev parent reply other threads:[~2022-02-24 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 13:31 [PATCH v2 0/3] soundwire: qcom: add pm runtime support Srinivas Kandagatla
2022-02-24 13:31 ` [PATCH v2 1/3] soundwire: qcom: add runtime pm support Srinivas Kandagatla
2022-02-24 15:41 ` Pierre-Louis Bossart
2022-02-24 15:58 ` Srinivas Kandagatla
2022-02-24 13:31 ` [PATCH v2 2/3] dt-bindings: soundwire: qcom: document optional wake irq Srinivas Kandagatla
2022-02-25 20:21 ` Rob Herring
2022-02-28 12:29 ` Srinivas Kandagatla
2022-02-24 13:31 ` [PATCH v2 3/3] soundwire: qcom: add in-band wake up interrupt support Srinivas Kandagatla
2022-02-24 15:44 ` Pierre-Louis Bossart [this message]
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=87f434b5-0e99-d1d1-e4d1-248cf35cd05c@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_srivasam@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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 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).