From: Stephen Boyd <swboyd@chromium.org>
To: Bjorn Andersson <andersson@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Guenter Roeck <linux@roeck-us.net>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-watchdog@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Andy Gross <agross@kernel.org>,
Sai Prakash Ranjan <quic_saipraka@quicinc.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/9] arm64: dts: qcom: sm8150: Make watchdog bark interrupt edge triggered
Date: Mon, 6 Nov 2023 13:50:28 -0800 [thread overview]
Message-ID: <CAE-0n51twrV24BE9aBNA8rA4y4J-Dpfh2ZnNMXdZEth-HGvbqA@mail.gmail.com> (raw)
In-Reply-To: <20231103163434.4.I23d0aa6c8f1fec5c26ad9b3c610df6f4c5392850@changeid>
Quoting Douglas Anderson (2023-11-03 16:34:30)
> As described in the patch ("arm64: dts: qcom: sc7180: Make watchdog
> bark interrupt edge triggered"), the Qualcomm watchdog timer's bark
> interrupt should be configured as edge triggered. Make the change.
>
> Fixes: b094c8f8dd2a ("arm64: dts: qcom: sm8150: Add watchdog bark interrupt")
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
next prev parent reply other threads:[~2023-11-06 21:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 23:34 [PATCH 1/9] arm64: dts: qcom: sc7180: Make watchdog bark interrupt edge triggered Douglas Anderson
2023-11-03 23:34 ` [PATCH 2/9] arm64: dts: qcom: sc7280: " Douglas Anderson
2023-11-04 0:42 ` Guenter Roeck
2023-11-06 21:49 ` Stephen Boyd
2023-11-03 23:34 ` [PATCH 3/9] arm64: dts: qcom: sdm845: " Douglas Anderson
2023-11-04 0:42 ` Guenter Roeck
2023-11-06 21:50 ` Stephen Boyd
2023-11-03 23:34 ` [PATCH 4/9] arm64: dts: qcom: sm8150: " Douglas Anderson
2023-11-04 0:42 ` Guenter Roeck
2023-11-06 21:50 ` Stephen Boyd [this message]
2023-11-03 23:34 ` [PATCH 5/9] arm64: dts: qcom: sm8250: " Douglas Anderson
2023-11-04 0:42 ` Guenter Roeck
2023-11-06 21:51 ` Stephen Boyd
2023-11-03 23:34 ` [PATCH 6/9] arm64: dts: qcom: sa8775p: " Douglas Anderson
2023-11-04 0:43 ` Guenter Roeck
2023-11-06 21:51 ` Stephen Boyd
2023-11-03 23:34 ` [PATCH 7/9] arm64: dts: qcom: sc8280xp: " Douglas Anderson
2023-11-04 0:43 ` Guenter Roeck
2023-11-06 21:52 ` Stephen Boyd
2023-11-03 23:34 ` [PATCH 8/9] arm64: dts: qcom: sm6350: " Douglas Anderson
2023-11-04 0:43 ` Guenter Roeck
2023-11-06 21:52 ` Stephen Boyd
2023-11-03 23:34 ` [PATCH 9/9] dt-bindings: watchdog: qcom-wdt: Make the interrupt example " Douglas Anderson
2023-11-04 0:43 ` Guenter Roeck
2023-11-05 13:33 ` Krzysztof Kozlowski
2023-11-06 21:53 ` Stephen Boyd
2023-11-04 0:42 ` [PATCH 1/9] arm64: dts: qcom: sc7180: Make watchdog bark interrupt " Guenter Roeck
2023-11-06 21:49 ` Stephen Boyd
2023-11-06 21:52 ` Doug Anderson
2023-11-06 22:36 ` 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=CAE-0n51twrV24BE9aBNA8rA4y4J-Dpfh2ZnNMXdZEth-HGvbqA@mail.gmail.com \
--to=swboyd@chromium.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.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_saipraka@quicinc.com \
--cc=robh+dt@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).