From: Guillaume LA ROQUE <glaroque@baylibre.com>
To: linux-omap@vger.kernel.org, nm@ti.com, vigneshr@ti.com
Cc: praneeth@ti.com, linux-arm-kernel@lists.infradead.org,
khilman@baylibre.com
Subject: Re: [PATCH v3] arm64: dts: ti: k3-am625-sk: enable ramoops
Date: Tue, 17 May 2022 14:27:53 +0200 [thread overview]
Message-ID: <d2af67be-7c71-8428-cffe-7dd012f381a6@baylibre.com> (raw)
In-Reply-To: <20220517122118.2976665-1-glaroque@baylibre.com>
please ignore, i do typo in commit message...
guillaume
Le 17/05/2022 à 14:21, Guillaume La Roque a écrit :
> Enable ramoops fetures to easily debug some issues.
>
> Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> ---
> Changes in :
> v3:
> - run dtbs_check
>
> v2:
> - Apply script create-mem_map.py with args given by Nishanth Menon
> - Spelling fix
> ---
> arch/arm64/boot/dts/ti/k3-am625-sk.dts | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am625-sk.dts b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> index 0de4113ccd5d..62d8503b5923 100644
> --- a/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> @@ -36,6 +36,15 @@ reserved-memory {
> #size-cells = <2>;
> ranges;
>
> + ramoops@9ca00000 {
> + compatible = "ramoops";
> + reg = <0x00 0x9ca00000 0x00 0x00100000>;
> + record-size = <0x8000>;
> + console-size = <0x8000>;
> + ftrace-size = <0x00>;
> + pmsg-size = <0x8000>;
> + };
> +
> secure_tfa_ddr: tfa@9e780000 {
> reg = <0x00 0x9e780000 0x00 0x80000>;
> alignment = <0x1000>;
> --
> 2.25.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-05-17 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 12:21 [PATCH v3] arm64: dts: ti: k3-am625-sk: enable ramoops Guillaume La Roque
2022-05-17 12:27 ` Guillaume LA ROQUE [this message]
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=d2af67be-7c71-8428-cffe-7dd012f381a6@baylibre.com \
--to=glaroque@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=vigneshr@ti.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