From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: Andy Gross <agross@kernel.org>,
David Brown <david.brown@linaro.org>,
Stephen Boyd <swboyd@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 2/4] soc: qcom: Add AOSS QMP driver
Date: Sat, 25 May 2019 11:17:14 -0700 [thread overview]
Message-ID: <20190525181714.GI2085@tuxbook-pro> (raw)
In-Reply-To: <3d2c61ca-b91b-fdc7-7837-af6a3b71af7e@codeaurora.org>
On Sat 25 May 10:53 PDT 2019, Sai Prakash Ranjan wrote:
> On 5/1/2019 10:07 AM, Bjorn Andersson wrote:
> > The Always On Subsystem (AOSS) Qualcomm Messaging Protocol (QMP) driver
> > is used to communicate with the AOSS for certain side-channel requests,
> > that are not available through the RPMh interface.
> >
> > The communication is a very simple synchronous mechanism of messages
> > being written in message RAM and a doorbell in the AOSS is rung. As the
> > AOSS has processed the message length is cleared and an interrupt is
> > fired by the AOSS as acknowledgment.
> >
> > The driver exposes the QDSS clock as a clock and the low-power state
> > associated with the remoteprocs in the system as a set of power-domains.
> >
> > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> > ---
> >
> > Changes since v6:
> > - Squash the pd into the same driver as the communication, to simplify
> > the interaction.
> > - Representing the QDSS clocks as a clock/power domain turns out to
> > cascade into a request to make all Coresight drivers have a secondary
> > compatible to replace the required bus clock with a required power
> > domain. So in v7 this is exposed as a clock instead.
> > - Some error checking updates, as reported by Doug.
> >
>
> Thanks for the patch Bjorn.
> Tested the QDSS functionality on SDM845 based Cheza board with this
> change and it works just fine.
>
> Tested-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Thanks for the confirmation Sai!
Regards,
Bjorn
next prev parent reply other threads:[~2019-05-25 18:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 4:37 [PATCH v7 0/4] Qualcomm AOSS QMP driver Bjorn Andersson
2019-05-01 4:37 ` [PATCH v7 1/4] dt-bindings: soc: qcom: Add AOSS QMP binding Bjorn Andersson
2019-05-01 19:42 ` Rob Herring
2019-05-21 10:42 ` Vinod Koul
2019-05-01 4:37 ` [PATCH v7 2/4] soc: qcom: Add AOSS QMP driver Bjorn Andersson
2019-05-13 14:10 ` Sibi Sankar
2019-05-21 8:08 ` Arun Kumar Neelakantam
2019-05-21 11:10 ` Vinod Koul
2019-05-23 16:38 ` Doug Anderson
2019-05-23 18:05 ` Stephen Boyd
2019-05-23 18:35 ` Doug Anderson
2019-05-23 19:09 ` Bjorn Andersson
2019-07-30 22:49 ` Stephen Boyd
2019-05-23 19:03 ` Bjorn Andersson
2019-05-25 17:53 ` Sai Prakash Ranjan
2019-05-25 18:17 ` Bjorn Andersson [this message]
2019-05-01 4:37 ` [PATCH v7 3/4] arm64: dts: qcom: Add AOSS QMP node Bjorn Andersson
2019-05-21 11:12 ` Vinod Koul
2019-05-23 15:12 ` Doug Anderson
2019-05-01 4:37 ` [PATCH v7 4/4] arm64: dts: qcom: sdm845: Add Q6V5 MSS node Bjorn Andersson
2019-05-21 11:13 ` Vinod Koul
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=20190525181714.GI2085@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=swboyd@chromium.org \
/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.