From: "Rob Herring (Arm)" <robh@kernel.org>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Tony Luck <tony.luck@intel.com>,
devicetree@vger.kernel.org,
Jonathan Hunter <jonathanh@nvidia.com>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, Kees Cook <kees@kernel.org>,
linux-tegra@vger.kernel.org, linux-hardening@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>
Subject: Re: [PATCH] arm64: tegra: Enable ramoops on Tegra210 and newer
Date: Mon, 07 Apr 2025 07:47:59 -0500 [thread overview]
Message-ID: <174402971861.1782962.14546127758047904369.robh@kernel.org> (raw)
In-Reply-To: <20250406-tegra-pstore-v1-1-bf5b57f12293@gmail.com>
On Sun, 06 Apr 2025 16:12:43 -0500, Aaron Kling wrote:
> This allows using pstore on all such platforms. There are some
> differences per arch:
>
> * Tegra132: Flounder does not appear to enumerate pstore and I do not
> have access to norrin, thus Tegra132 is left out of this commit.
> * Tegra210: Does not support ramoops carveouts in the bootloader, instead
> relying on a dowstream driver to allocate the carveout, hence this
> hardcodes a location matching what the downstream driver picks.
> * Tegra186 and Tegra194 on cboot: Bootloader fills in the address and
> size in a node specifically named /reserved-memory/ramoops_carveout,
> thus these cannot be renamed.
> * Tegra194 and Tegra234 on edk2: Bootloader looks up the node based on
> compatible, however the dt still does not know the address, so keeping
> the node name consistent on Tegra186 and newer.
>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 16 ++++++++++++++++
> arch/arm64/boot/dts/nvidia/tegra194.dtsi | 16 ++++++++++++++++
> arch/arm64/boot/dts/nvidia/tegra210.dtsi | 13 +++++++++++++
> arch/arm64/boot/dts/nvidia/tegra234.dtsi | 16 ++++++++++++++++
> 4 files changed, 61 insertions(+)
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
This patch series was applied (using b4) to base:
Base: using specified base-commit 91e5bfe317d8f8471fbaa3e70cf66cae1314a516
If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)
New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/nvidia/' for 20250406-tegra-pstore-v1-1-bf5b57f12293@gmail.com:
arch/arm64/boot/dts/nvidia/tegra186-p2771-0000.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
arch/arm64/boot/dts/nvidia/tegra234-sim-vdk.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
arch/arm64/boot/dts/nvidia/tegra194-p3509-0000+p3668-0000.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
arch/arm64/boot/dts/nvidia/tegra234-p3768-0000+p3767-0000.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
arch/arm64/boot/dts/nvidia/tegra234-p3740-0002+p3701-0008.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0008.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
arch/arm64/boot/dts/nvidia/tegra186-p3509-0000+p3636-0001.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
arch/arm64/boot/dts/nvidia/tegra194-p2972-0000.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
arch/arm64/boot/dts/nvidia/tegra234-p3768-0000+p3767-0005.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
arch/arm64/boot/dts/nvidia/tegra194-p3509-0000+p3668-0001.dtb: ramoops_carveout (ramoops): 'reg' is a required property
from schema $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
next prev parent reply other threads:[~2025-04-07 12:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 21:12 [PATCH] arm64: tegra: Enable ramoops on Tegra210 and newer Aaron Kling
2025-04-06 21:12 ` Aaron Kling via B4 Relay
2025-04-07 12:47 ` Rob Herring (Arm) [this message]
2025-04-07 12:59 ` Krzysztof Kozlowski
2025-04-07 16:00 ` Aaron Kling
2025-04-08 6:07 ` Krzysztof Kozlowski
2025-04-08 7:35 ` Aaron Kling
2025-04-08 8:17 ` Krzysztof Kozlowski
2025-04-08 8:49 ` Aaron Kling
2025-04-21 1:45 ` Aaron Kling
2025-04-29 1:21 ` Aaron Kling
2025-05-08 21:27 ` Thierry Reding
2025-05-28 17:35 ` Aaron Kling
2025-05-29 8:52 ` Krzysztof Kozlowski
2025-06-30 18:48 ` Aaron Kling
2025-07-03 7:24 ` Thierry Reding
2025-07-14 6:01 ` Aaron Kling
2025-07-31 21:24 ` Aaron Kling
2025-08-01 9:49 ` Thierry Reding
2025-05-08 21:33 ` Thierry Reding
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=174402971861.1782962.14546127758047904369.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=jonathanh@nvidia.com \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tony.luck@intel.com \
--cc=webgeek1234@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.