devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy McNicoll <jmcnicol@redhat.com>
To: zhuoweizhang@yahoo.com
Cc: jeremymc@redhat.com, Andy Gross <andy.gross@linaro.org>,
	David Brown <david.brown@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Kees Cook <keescook@chromium.org>,
	Anton Vorontsov <anton@enomsg.org>,
	Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
	linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: angler: add pstore-ramoops support
Date: Thu, 11 Jan 2018 18:33:55 -0800	[thread overview]
Message-ID: <20180112023354.GA16005@mini-rhel.redhat.com> (raw)
In-Reply-To: <1514446709-19347-1-git-send-email-zhuoweizhang@yahoo.com>

On Thu, Dec 28, 2017 at 02:38:29AM -0500, zhuoweizhang@yahoo.com wrote:
> From: Zhuowei Zhang <zhuoweizhang@yahoo.com>
> 
> Support pstore-ramoops for retrieving kernel oops and panics after reboot.
> 
> The address and configs are taken from the downstream kernel's device tree.
> 
> Signed-off-by: Zhuowei Zhang <zhuoweizhang@yahoo.com>
> ---
>  arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts b/arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts
> index dfa08f5..9ce3a6e 100644
> --- a/arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts
> +++ b/arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts
> @@ -37,4 +37,19 @@
>  			pinctrl-1 = <&blsp1_uart2_sleep>;
>  		};
>  	};
> +
> +	reserved-memory {
> +		#address-cells = <2>;
> +		#size-cells = <2>;
> +		ranges;
> +
> +		ramoops@1fe00000 {
> +			compatible = "ramoops";
> +			reg = <0 0x1fe00000 0 0x00200000>;

Downstream doesn't use 0x0 to denote 0.  I am fine with this, if 
someone has a concern or issue with it we can change it before merging.


> +			console-size = <0x100000>;
> +			record-size = <0x10000>;
> +			ftrace-size = <0x10000>;
> +			pmsg-size = <0x80000>;

We could pad this with leading 0's but I find this much easier
to read.

> +		};
> +	};
>  };

Thank you very much for taking the time to send this.  


Acked-by: Jeremy McNicoll <jeremymc@redhat.com>

  parent reply	other threads:[~2018-01-12  2:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28  7:38 [PATCH] arm64: dts: angler: add pstore-ramoops support zhuoweizhang
2018-01-02 18:09 ` Kees Cook
2018-01-12  2:33 ` Jeremy McNicoll [this message]
2018-02-02 19:27   ` Bjorn Andersson

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=20180112023354.GA16005@mini-rhel.redhat.com \
    --to=jmcnicol@redhat.com \
    --cc=andy.gross@linaro.org \
    --cc=anton@enomsg.org \
    --cc=catalin.marinas@arm.com \
    --cc=ccross@android.com \
    --cc=david.brown@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jeremymc@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=will.deacon@arm.com \
    --cc=zhuoweizhang@yahoo.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;
as well as URLs for NNTP newsgroup(s).