From: Pavan Kondeti <pavan.kondeti@oss.qualcomm.com>
To: Pavan Kondeti <pavan.kondeti@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>,
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>,
linux-arm-msm@vger.kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v4 1/2] soc: qcom: smem: Register gunyah watchdog device
Date: Wed, 5 Nov 2025 17:41:43 +0530 [thread overview]
Message-ID: <729d0806-0f92-45a3-ae36-307513f8b808@quicinc.com> (raw)
In-Reply-To: <2ef1d795-5cdd-4465-9333-16a02207a806@quicinc.com>
On Tue, Nov 04, 2025 at 10:33:52AM +0530, Pavan Kondeti wrote:
>
> > I presume if we determine that Gunyah is present, and we haven't put
> > sbsa wdt in place (e.g. during bringup) Gunyah and Gunyah WDT will
> > handle the outcome gracefully...
> >
> Yes, we are told Gunyah support SMCC based WDT even if it emulates
> SBSA. Most importantly, we have STATUS SMC in gunyah-wdt probe before
> registering the watchdog device.
>
Thanks Bjorn for asking this question. I have tested this scenario on
Kaanapali. Since the initial platform support patches have added
watchdog device, I don't see gunyah-wdt platform device created. When I
removed the node, I see gunyah-wdt platform device is created and the
driver is probed successfully.
Since this patch checks the device node presence via
of_find_compatible_node(), it does not cover the case where the node is
present but marked as disabled/reserved etc. I think it would be good
to add of_device_is_available() check as well to cover this case.
Thanks,
Pavan
next prev parent reply other threads:[~2025-11-05 12:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 10:18 [PATCH v4 0/2] Add support for Gunyah Watchdog Hrishabh Rajput via B4 Relay
2025-10-31 10:18 ` [PATCH v4 1/2] soc: qcom: smem: Register gunyah watchdog device Hrishabh Rajput via B4 Relay
2025-10-31 14:40 ` Dmitry Baryshkov
2025-10-31 15:24 ` Guenter Roeck
2025-11-01 18:50 ` Bjorn Andersson
2025-11-03 9:53 ` Hrishabh Rajput
2025-11-04 0:38 ` Bjorn Andersson
2025-11-03 9:50 ` Hrishabh Rajput
2025-11-01 18:45 ` Bjorn Andersson
2025-11-03 10:33 ` Hrishabh Rajput
2025-11-04 1:01 ` Bjorn Andersson
2025-11-04 3:30 ` Pavan Kondeti
2025-11-04 3:52 ` Bjorn Andersson
2025-11-04 5:03 ` Pavan Kondeti
2025-11-05 12:11 ` Pavan Kondeti [this message]
2025-10-31 10:18 ` [PATCH v4 2/2] watchdog: Add driver for Gunyah Watchdog Hrishabh Rajput via B4 Relay
2025-10-31 11:48 ` Krzysztof Kozlowski
2025-10-31 12:11 ` Pavan Kondeti
2025-10-31 12:39 ` Krzysztof Kozlowski
2025-10-31 13:19 ` Pavan Kondeti
2025-10-31 14:36 ` Dmitry Baryshkov
2025-10-31 15:42 ` Guenter Roeck
2025-11-03 11:25 ` Hrishabh Rajput
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=729d0806-0f92-45a3-ae36-307513f8b808@quicinc.com \
--to=pavan.kondeti@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=hrishabh.rajput@oss.qualcomm.com \
--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=neil.armstrong@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®