Linux-Watchdog Archive mirror
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@linux-watchdog.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	swboyd@chromium.org, linux-watchdog@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.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 v2 9/9] dt-bindings: watchdog: qcom-wdt: Make the interrupt example edge triggered
Date: Sun, 17 Dec 2023 16:33:18 +0100	[thread overview]
Message-ID: <20231217153318.GA6196@www.linux-watchdog.org> (raw)
In-Reply-To: <CAD=FV=XsPGvNggpJPCpF=xhkm3dOHsStycZvuVttA=ZH6=EUmw@mail.gmail.com>

Hi Doug,

> Hi,
> 
> On Mon, Nov 6, 2023 at 2:44 PM Douglas Anderson <dianders@chromium.org> wrote:
> >
> > 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.
> >
> > Update the example in the bindings.
> >
> > Fixes: 7c631cdff391 ("dt-bindings: watchdog: qcom-wdt: allow interrupts")
> > Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> > Signed-off-by: Douglas Anderson <dianders@chromium.org>
> > ---
> >
> > (no changes since v1)
> >
> >  Documentation/devicetree/bindings/watchdog/qcom-wdt.yaml | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> I saw Bjorn landed all of the dts patches from this series but it
> looks like the bindings patch got left behind. Anyone want to claim it
> for their tree, or Ack it saying that you'd prefer for it to go
> through someone else's tree? I assume Krzysztof's Ack means he's not
> intending for it to go through the DT tree and Bjorn doesn't seem to
> intend for it to go through the Qualcomm tree. Guenter/Wim: it feels
> like this could go in the watchdog tree?

I picked it up in the watchdog tree.

Kind regards,
Wim.


  reply	other threads:[~2023-12-17 15:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 22:43 [PATCH v2 1/9] arm64: dts: qcom: sc7180: Make watchdog bark interrupt edge triggered Douglas Anderson
2023-11-06 22:43 ` [PATCH v2 2/9] arm64: dts: qcom: sc7280: " Douglas Anderson
2023-11-06 22:43 ` [PATCH v2 3/9] arm64: dts: qcom: sdm845: " Douglas Anderson
2023-11-06 22:43 ` [PATCH v2 4/9] arm64: dts: qcom: sm8150: " Douglas Anderson
2023-11-06 22:43 ` [PATCH v2 5/9] arm64: dts: qcom: sm8250: " Douglas Anderson
2023-11-06 22:43 ` [PATCH v2 6/9] arm64: dts: qcom: sa8775p: " Douglas Anderson
2023-11-07  7:40   ` Bartosz Golaszewski
2023-11-06 22:43 ` [PATCH v2 7/9] arm64: dts: qcom: sc8280xp: " Douglas Anderson
2023-11-16  8:22   ` Johan Hovold
2023-11-06 22:43 ` [PATCH v2 8/9] arm64: dts: qcom: sm6350: " Douglas Anderson
2023-11-06 22:43 ` [PATCH v2 9/9] dt-bindings: watchdog: qcom-wdt: Make the interrupt example " Douglas Anderson
2023-12-08 15:34   ` Doug Anderson
2023-12-17 15:33     ` Wim Van Sebroeck [this message]
2023-12-08  2:57 ` (subset) [PATCH v2 1/9] arm64: dts: qcom: sc7180: Make watchdog bark interrupt " 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=20231217153318.GA6196@www.linux-watchdog.org \
    --to=wim@linux-watchdog.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=krzysztof.kozlowski@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=swboyd@chromium.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).