From: Zhenhua Huang <quic_zhenhuah@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.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: Mon, 23 Oct 2023 20:18:58 +0800 [thread overview]
Message-ID: <10848e69-b994-b562-d5d3-25a7ca40cb97@quicinc.com> (raw)
In-Reply-To: <70072874-6fa8-46ba-bf26-c35aa6ec7bb6@linaro.org>
On 2023/10/23 17:25, Krzysztof Kozlowski wrote:
> On 23/10/2023 11:20, Zhenhua Huang wrote:
>> Qualcomm memory dump driver is to cooperate with firmware, providing the
>> hints(id and size) of storing useful debugging information into pre-allocated
>> memory. Firmware then does the real data capture. The debugging information
>> includes cache contents, internal memory, registers.
>>
>> The driver dynamically reserves memory and provides the hints(dump id and size)
>> following specified protocols with firmware. After crash and warm reboot,
>> firmware scans these information and stores contents into reserved memory
>> accordingly. Firmware then enters into full dump mode which dumps whole DDR
>> to host through USB.
>
> How does it relate to minidump?
Minidump is used for dumping *software* related data/information. While
the memory dump is used to communicate with firmware to dump *hardware*
related information.
>
>>
>> User then get full dump using PCAT and can parse out these informations.
>>
>> Dump id and size are provided by bootconfig. The expected format of a
>> bootconfig file is as follows:-
>> memory_dump_config {
>> <node name> {
>> id = <id of HW component>
>> size = <dump size of HW component>
>> }
>> }
>>
>> for example:
>> memory_dump_config {
>> c0_context_dump {
>> id = 0
>> size = 0x800
>> }
>> }
>>
>> Test based on 6.6-rc1.
>
> I don't think so (or you miss yamllint).
>
> $ git checkout v6.6-rc1
> $ b4 am...
> $ dt_binding_chec
Apologize for this. I actually run it but seems some mistakes here, will
be more careful next time.
>
> qcom,mem-dump.yaml:5:10: [error] string value is redundantly quoted with
> any quotes (quoted-strings)
>
>
> Best regards,
> Krzysztof
>
Thanks,
Zhenhua
next prev parent reply other threads:[~2023-10-23 12:19 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 [this message]
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
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=10848e69-b994-b562-d5d3-25a7ca40cb97@quicinc.com \
--to=quic_zhenhuah@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=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_tingweiz@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®