From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH 1/4] arm64: dts: qcom: sm6115-j606f: Add ramoops node
Date: Thu, 6 Apr 2023 20:29:52 +0200 [thread overview]
Message-ID: <eacc380a-aa33-5b1d-0a11-124b584cd1aa@linaro.org> (raw)
In-Reply-To: <9554be2b-c80d-8c5b-48e3-2508a7b4ecd1@linaro.org>
On 6.04.2023 19:54, Dmitry Baryshkov wrote:
> On 06/04/2023 18:25, Konrad Dybcio wrote:
>> Add a ramoops node to enable retrieving crash logs.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>> ---
>> arch/arm64/boot/dts/qcom/sm6115p-lenovo-j606f.dts | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sm6115p-lenovo-j606f.dts b/arch/arm64/boot/dts/qcom/sm6115p-lenovo-j606f.dts
>> index 10c9d338446c..fd064899791c 100644
>> --- a/arch/arm64/boot/dts/qcom/sm6115p-lenovo-j606f.dts
>> +++ b/arch/arm64/boot/dts/qcom/sm6115p-lenovo-j606f.dts
>> @@ -52,6 +52,17 @@ key-volume-up {
>> wakeup-source;
>> };
>> };
>> +
>> + reserved-memory {
>> + ramoops@ffc00000 {
>> + compatible = "ramoops";
>> + reg = <0x0 0xffc00000 0x0 0x100000>;
>> + record-size = <0x1000>;
>> + console-size = <0x40000>;
>
> no ftrace-size?
It could use some!
>
>> + ecc-size = <16>;
>> + no-map;
>
> I see that other ramoops defines are not marked with no-map. Is there any reason for that?
Hm, not really. I can get rid of it for v2.
Konrad
>
>> + };
>> + };
>> };
>> &dispcc {
>>
>
next prev parent reply other threads:[~2023-04-06 18:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 15:25 [PATCH 0/4] Tab P11 features Konrad Dybcio
2023-04-06 15:25 ` [PATCH 1/4] arm64: dts: qcom: sm6115-j606f: Add ramoops node Konrad Dybcio
2023-04-06 17:54 ` Dmitry Baryshkov
2023-04-06 18:29 ` Konrad Dybcio [this message]
2023-04-06 15:25 ` [PATCH 2/4] arm64: dts: qcom: sm6115: Add RMTFS Konrad Dybcio
2023-04-06 17:52 ` Dmitry Baryshkov
2023-04-06 15:25 ` [PATCH 3/4] arm64: dts: qcom: sm6115p-j606f: Enable remoteprocs Konrad Dybcio
2023-04-06 17:51 ` Dmitry Baryshkov
2023-04-06 15:25 ` [PATCH 4/4] arm64: dts: qcom: sm6115p-j606f: Enable ATH10K WiFi Konrad Dybcio
2023-04-06 17:51 ` Dmitry Baryshkov
2023-04-06 18:32 ` Konrad Dybcio
2023-04-06 18:56 ` Dmitry Baryshkov
2023-04-07 13:27 ` Dmitry Baryshkov
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=eacc380a-aa33-5b1d-0a11-124b584cd1aa@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robh+dt@kernel.org \
--cc=tony.luck@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
all inboxes | Powered by JetHome®