From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Zhenhua Huang <quic_zhenhuah@quicinc.com>,
Konrad Dybcio <konrad.dybcio@linaro.org>, <agross@kernel.org>,
<andersson@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel@quicinc.com>,
<quic_tingweiz@quicinc.com>
Subject: Re: [PATCH v1 0/5] soc/arm64: qcom: add initial version of memory dump
Date: Tue, 24 Oct 2023 07:25:03 -0700 [thread overview]
Message-ID: <fc0bbd15-209e-412d-a132-6aac2e871c71@quicinc.com> (raw)
In-Reply-To: <ac42f27e-007d-1157-ae46-403420d9fdcb@quicinc.com>
On 10/24/2023 3:10 AM, Zhenhua Huang wrote:
>
>
> On 2023/10/23 21:50, Konrad Dybcio wrote:
>> On 23.10.2023 11:20, Zhenhua Huang wrote:
>>> Qualcomm memory dump driver is to cooperate with firmware, providing the
>> Firmware == The hypervisor? The TZ? Some uncore chip?
>
> It's part of bootloader which also needs to cooperate with TZ. After
> system crash and warm reset, system enters debug mode which needs the
> dump table.
When you re-spin can you be clear about for which firmware this is
applicable? On a Qualcomm SoC there are multiple integrated peripherals
with their own firmware, so it is important to clarify which ones can
utilize this framework.
/jeff
next prev parent reply other threads:[~2023-10-24 14:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 9:20 Zhenhua Huang
2023-10-23 9:20 ` [PATCH v1 1/5] dt-bindings: soc: qcom: Add memory_dump driver bindings Zhenhua Huang
2023-10-23 9:27 ` Krzysztof Kozlowski
2023-10-23 11:54 ` Zhenhua Huang
2023-10-23 12:52 ` Krzysztof Kozlowski
2023-10-24 10:57 ` Zhenhua Huang
2023-10-24 13:55 ` Krzysztof Kozlowski
2023-10-26 21:01 ` Elliot Berman
2023-10-23 17:40 ` Rob Herring
2023-10-23 9:20 ` [PATCH v1 2/5] dt-bindings: sram: qcom,imem: document sm8250 Zhenhua Huang
2023-10-23 9:27 ` Krzysztof Kozlowski
2023-10-23 17:40 ` Rob Herring
2023-10-24 11:07 ` Zhenhua Huang
2023-10-23 9:20 ` [PATCH v1 3/5] soc: qcom: memory_dump: Add memory dump driver Zhenhua Huang
2023-10-23 9:31 ` Krzysztof Kozlowski
2023-10-23 11:43 ` Zhenhua Huang
2023-10-23 11:46 ` Krzysztof Kozlowski
2023-10-23 12:19 ` Zhenhua Huang
2023-10-23 12:53 ` Krzysztof Kozlowski
2023-10-24 10:57 ` Zhenhua Huang
2023-10-24 13:58 ` Krzysztof Kozlowski
2023-10-23 13:56 ` Konrad Dybcio
2023-10-24 7:36 ` Zhenhua Huang
2023-10-26 18:58 ` kernel test robot
2023-10-23 9:20 ` [PATCH v1 4/5] arm64: defconfig: enable Qcom Memory Dump driver Zhenhua Huang
2023-10-23 9:32 ` Krzysztof Kozlowski
2023-10-23 11:43 ` Zhenhua Huang
2023-10-23 11:47 ` Krzysztof Kozlowski
2023-10-23 12:19 ` Zhenhua Huang
2023-10-23 9:20 ` [PATCH v1 5/5] arm64: dts: qcom: sm8250: Add memory dump node Zhenhua Huang
2023-10-23 9:33 ` Krzysztof Kozlowski
2023-10-23 9:25 ` [PATCH v1 0/5] soc/arm64: qcom: add initial version of memory dump Krzysztof Kozlowski
2023-10-23 12:18 ` Zhenhua Huang
2023-10-23 12:54 ` Krzysztof Kozlowski
2023-10-23 13:50 ` Konrad Dybcio
2023-10-24 10:10 ` Zhenhua Huang
2023-10-24 14:25 ` Jeff Johnson [this message]
2023-10-23 14:31 ` Caleb Connolly
2023-10-24 9:53 ` Zhenhua Huang
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=fc0bbd15-209e-412d-a132-6aac2e871c71@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_zhenhuah@quicinc.com \
--cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®