From: Petlozu Pravareshwar <petlozup@nvidia.com>
To: <thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <p.zabel@pengutronix.de>,
<dmitry.osipenko@collabora.com>, <ulf.hansson@linaro.org>,
<kkartik@nvidia.com>, <cai.huoqing@linux.dev>,
<spatra@nvidia.com>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: <petlozup@nvidia.com>
Subject: [PATCH 2/3] dt-bindings: tegra: pmc: Update scratch as an optional aperture
Date: Sat, 6 Jan 2024 07:51:33 +0000 [thread overview]
Message-ID: <20240106075134.3933491-2-petlozup@nvidia.com> (raw)
In-Reply-To: <20240106075134.3933491-1-petlozup@nvidia.com>
Scratch address space register is used to store reboot reason. For
some Tegra234 systems, the scratch space is not available to store
the reboot reason. This is because scratch region on these systems
is not accessible by the kernel as restricted by the Hypervisor.
Such systems would delist scratch aperture from PMC DT node.
Accordingly, this change makes "scratch" as an optional aperture for
Tegra234 in PMC dt-binding document.
Signed-off-by: Petlozu Pravareshwar <petlozup@nvidia.com>
---
.../arm/tegra/nvidia,tegra186-pmc.yaml | 83 +++++++++++++------
1 file changed, 58 insertions(+), 25 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.yaml b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.yaml
index 0faa403f68c8..2716610a1a02 100644
--- a/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.yaml
+++ b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.yaml
@@ -23,12 +23,7 @@ properties:
reg-names:
minItems: 4
- items:
- - const: pmc
- - const: wake
- - const: aotag
- - const: scratch
- - const: misc
+ maxItems: 5
interrupt-controller: true
@@ -41,25 +36,63 @@ properties:
description: If present, inverts the PMU interrupt signal.
$ref: /schemas/types.yaml#/definitions/flag
-if:
- properties:
- compatible:
- contains:
- const: nvidia,tegra186-pmc
-then:
- properties:
- reg:
- maxItems: 4
-
- reg-names:
- maxItems: 4
-else:
- properties:
- reg:
- minItems: 5
-
- reg-names:
- minItems: 5
+allOf:
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: nvidia,tegra186-pmc
+ then:
+ properties:
+ reg:
+ maxItems: 4
+ reg-names:
+ items:
+ - const: pmc
+ - const: wake
+ - const: aotag
+ - const: scratch
+
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: nvidia,tegra194-pmc
+ then:
+ properties:
+ reg:
+ minItems: 5
+ reg-names:
+ items:
+ - const: pmc
+ - const: wake
+ - const: aotag
+ - const: scratch
+ - const: misc
+
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: nvidia,tegra234-pmc
+ then:
+ properties:
+ reg:
+ minItems: 4
+ maxItems: 5
+ reg-names:
+ anyOf:
+ - items:
+ - const: pmc
+ - const: wake
+ - const: aotag
+ - const: misc
+ - items:
+ - const: pmc
+ - const: wake
+ - const: aotag
+ - const: scratch
+ - const: misc
patternProperties:
"^[a-z0-9]+-[a-z0-9]+$":
--
2.17.1
next prev parent reply other threads:[~2024-01-06 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 7:51 [PATCH 1/3] soc/tegra: pmc: Update address mapping sequence for PMC apertures Petlozu Pravareshwar
2024-01-06 7:51 ` Petlozu Pravareshwar [this message]
2024-01-06 9:51 ` [PATCH 2/3] dt-bindings: tegra: pmc: Update scratch as an optional aperture Rob Herring
2024-01-17 15:41 ` Petlozu Pravareshwar
2024-01-08 16:16 ` kernel test robot
2024-01-08 19:58 ` Rob Herring
2024-01-17 15:46 ` Petlozu Pravareshwar
2024-01-06 7:51 ` [PATCH 3/3] soc/tegra: " Petlozu Pravareshwar
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=20240106075134.3933491-2-petlozup@nvidia.com \
--to=petlozup@nvidia.com \
--cc=cai.huoqing@linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=jonathanh@nvidia.com \
--cc=kkartik@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=spatra@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.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 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.