From: Maulik Shah <mkshah@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Stephen Boyd <swboyd@chromium.org>
Cc: evgreen@chromium.org, mka@chromium.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
agross@kernel.org, dianders@chromium.org, linux@roeck-us.net,
rnayak@codeaurora.org, lsrao@codeaurora.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v8 3/5] arm64: dts: qcom: sc7180: Enable SoC sleep stats
Date: Sun, 5 Sep 2021 18:29:29 +0530 [thread overview]
Message-ID: <f80b2317-c234-0439-b6ae-dffb040f22be@codeaurora.org> (raw)
In-Reply-To: <YLxEPkQdKKYNDHqv@builder.lan>
Hi,
On 6/6/2021 9:12 AM, Bjorn Andersson wrote:
> Yes, "ram" sounds like a better node name for both the qmp and
> sleep-stats region - in the RPMH case.
Updated to use "aop_msgram" in v9. I think saying only "ram" may
further confuse with DDR.
Thanks,
Maulik
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2021-09-05 12:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 11:26 [PATCH v8 0/5] Introduce SoC sleep stats driver Maulik Shah
2021-05-21 11:26 ` [PATCH v8 1/5] dt-bindings: Introduce SoC sleep stats bindings Maulik Shah
2021-05-21 11:26 ` [PATCH v8 2/5] soc: qcom: Add SoC sleep stats driver Maulik Shah
2021-05-26 23:45 ` Stephen Boyd
2021-09-05 12:59 ` Maulik Shah
2021-05-31 17:30 ` Bjorn Andersson
2021-05-21 11:26 ` [PATCH v8 3/5] arm64: dts: qcom: sc7180: Enable SoC sleep stats Maulik Shah
2021-05-26 23:30 ` Stephen Boyd
2021-05-31 17:57 ` Bjorn Andersson
2021-06-03 0:26 ` Stephen Boyd
2021-06-03 2:44 ` Bjorn Andersson
2021-06-04 21:53 ` Stephen Boyd
2021-06-06 3:42 ` Bjorn Andersson
2021-09-05 12:59 ` Maulik Shah [this message]
2021-05-21 11:26 ` [PATCH v8 4/5] arm64: defconfig: Enable SoC sleep stats driver Maulik Shah
2021-05-26 23:30 ` Stephen Boyd
2021-05-21 11:26 ` [PATCH v8 5/5] arm64: dts: qcom: sc7280: Enable SoC sleep stats Maulik Shah
2021-05-26 23:30 ` Stephen Boyd
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=f80b2317-c234-0439-b6ae-dffb040f22be@codeaurora.org \
--to=mkshah@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lsrao@codeaurora.org \
--cc=mka@chromium.org \
--cc=rnayak@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.