From: Guenter Roeck <linux@roeck-us.net>
To: hrishabh.rajput@oss.qualcomm.com,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Pavan Kondeti <pavan.kondeti@oss.qualcomm.com>,
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: Fri, 31 Oct 2025 08:24:44 -0700 [thread overview]
Message-ID: <9421ff80-bd86-4b29-baca-c86da90c91aa@roeck-us.net> (raw)
In-Reply-To: <20251031-gunyah_watchdog-v4-1-7abb1ee11315@oss.qualcomm.com>
On 10/31/25 03:18, Hrishabh Rajput via B4 Relay wrote:
> From: Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>
>
> To restrict gunyah watchdog initialization to Qualcomm platforms,
> register the watchdog device in the SMEM driver.
>
> When Gunyah is not present or Gunyah emulates MMIO-based
> watchdog, we expect Qualcomm watchdog or ARM SBSA watchdog device to be
> present in the devicetree. If none of these device nodes are detected,
> we register the SMC-based Gunyah watchdog device.
>
There should also be an explanation why there is no "qcom,gunyah-wdt"
devicetree node, both here and in the file.
> Signed-off-by: Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>
> ---
> drivers/soc/qcom/smem.c | 37 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
>
> diff --git a/drivers/soc/qcom/smem.c b/drivers/soc/qcom/smem.c
> index cf425930539e..40e4749fab02 100644
> --- a/drivers/soc/qcom/smem.c
> +++ b/drivers/soc/qcom/smem.c
> @@ -1118,6 +1118,34 @@ static int qcom_smem_resolve_mem(struct qcom_smem *smem, const char *name,
> return 0;
> }
>
> +static int register_gunyah_wdt_device(void)
> +{
> + struct platform_device *gunyah_wdt_dev;
> + struct device_node *np;
> +
> + /*
> + * When Gunyah is not present or Gunyah is emulating a memory-mapped
> + * watchdog, either of Qualcomm watchdog or ARM SBSA watchdog will be
> + * present. Skip initialization of SMC-based Gunyah watchdog if that is
> + * the case.
> + */
> + np = of_find_compatible_node(NULL, NULL, "qcom,kpss-wdt");
> + if (np) {
> + of_node_put(np);
> + return 0;
> + }
> +
> + np = of_find_compatible_node(NULL, NULL, "arm,sbsa-gwdt");
> + if (np) {
> + of_node_put(np);
> + return 0;
> + }
> +
> + gunyah_wdt_dev = platform_device_register_simple("gunyah-wdt", -1,
> + NULL, 0);
> + return PTR_ERR_OR_ZERO(gunyah_wdt_dev);
> +}
> +
> static int qcom_smem_probe(struct platform_device *pdev)
> {
> struct smem_header *header;
> @@ -1236,11 +1264,20 @@ static int qcom_smem_probe(struct platform_device *pdev)
> if (IS_ERR(smem->socinfo))
> dev_dbg(&pdev->dev, "failed to register socinfo device\n");
>
> + ret = register_gunyah_wdt_device();
> + if (ret)
> + dev_dbg(&pdev->dev, "failed to register watchdog device\n");
> +
> return 0;
> }
>
> static void qcom_smem_remove(struct platform_device *pdev)
> {
> + /*
> + * Gunyah watchdog is intended to be a persistent module. Hence, the
> + * watchdog device is not unregistered.
> + */
> +
Odd explanation. I would assume that the smem device is supposed to be
persistent as well. Since that is not the case, what happens if _this_
device is unregistered and registered again ?
Guenter
> platform_device_unregister(__smem->socinfo);
>
> hwspin_lock_free(__smem->hwlock);
>
next prev parent reply other threads:[~2025-10-31 15:24 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 [this message]
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
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=9421ff80-bd86-4b29-baca-c86da90c91aa@roeck-us.net \
--to=linux@roeck-us.net \
--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=neil.armstrong@linaro.org \
--cc=pavan.kondeti@oss.qualcomm.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 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®