From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: x1-el2: Add the APSS watchdog
Date: Thu, 18 Dec 2025 11:06:08 +0100 [thread overview]
Message-ID: <aUPSEM2AFPTmQLtv@linaro.org> (raw)
In-Reply-To: <20251214-arm64-dts-qcom-x1e80100-el2-add-apss-wdt-v1-2-94ee80b8cbe7@oss.qualcomm.com>
On Sun, Dec 14, 2025 at 10:49:59PM +0200, Abel Vesa wrote:
> The watchdog support in EL1 is SBSA compliant, handled by Gunyah
> hypervisor, but in EL2. the watchdog is an instance of the APSS WDT HW
> block, same as older platforms. So describe the APSS WDT node in the EL2
> overlay.
>
> Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
> ---
> arch/arm64/boot/dts/qcom/x1-el2.dtso | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/x1-el2.dtso b/arch/arm64/boot/dts/qcom/x1-el2.dtso
> index 2d1c9151cf1b..404174a15659 100644
> --- a/arch/arm64/boot/dts/qcom/x1-el2.dtso
> +++ b/arch/arm64/boot/dts/qcom/x1-el2.dtso
> @@ -7,6 +7,8 @@
> /dts-v1/;
> /plugin/;
>
> +#include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> /* We can't and don't need to use zap shader in EL2 as linux can zap the gpu on it's own. */
> &gpu_zap_shader {
> status = "disabled";
> @@ -55,3 +57,17 @@ &pcie_smmu {
> &sbsa_watchdog {
> status = "disabled";
> };
> +
> +&soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + /* The APSS watchdog is only accessible in EL2 */
> + watchdog@17410000 {
> + compatible = "qcom,apss-wdt-x1e80100", "qcom,kpss-wdt";
> + reg = <0x0 0x17410000 0x0 0x1000>;
> + clocks = <&sleep_clk>;
> + interrupts = <GIC_SPI 0 IRQ_TYPE_EDGE_RISING>;
> + interrupt-parent = <&intc>;
> + };
For consistency with &pcie_smmu, I think it would be cleaner to put this
into hamoa.dtsi, mark it as status = "reserved"; and then enable it here
in the overlay. That way, we have a full hardware description in
hamoa.dtsi.
You should also be able to drop the interrupt-parent if you move it
there.
Thanks,
Stephan
next prev parent reply other threads:[~2025-12-18 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 20:49 [PATCH 0/2] arm64: dts: qcom: x1e80100: Enable APSS watchdog in EL2 Abel Vesa
2025-12-14 20:49 ` [PATCH 1/2] dt-bindings: watchdog: Document X1E80100 compatible Abel Vesa
2025-12-17 1:01 ` Rob Herring (Arm)
2025-12-14 20:49 ` [PATCH 2/2] arm64: dts: qcom: x1-el2: Add the APSS watchdog Abel Vesa
2025-12-15 20:53 ` Dmitry Baryshkov
2025-12-18 10:06 ` Stephan Gerhold [this message]
2025-12-18 22:11 ` Abel Vesa
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=aUPSEM2AFPTmQLtv@linaro.org \
--to=stephan.gerhold@linaro.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=quic_rjendra@quicinc.com \
--cc=robh@kernel.org \
--cc=wim@linux-watchdog.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.