From: Pavan Kondeti <pavan.kondeti@oss.qualcomm.com>
To: Pavan Kondeti <pavan.kondeti@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Konrad Dybcio <konradybcio@kernel.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>,
Shivendra Pratap <shivendra.pratap@oss.qualcomm.com>
Subject: Re: [PATCH v8 0/2] Add support for Gunyah Watchdog
Date: Tue, 3 Mar 2026 10:53:36 +0530 [thread overview]
Message-ID: <4427f335-bb50-44af-94a5-142d8355a705@quicinc.com> (raw)
In-Reply-To: <c5a57ab6-ad6c-4228-8ccb-7d7ef306b5b8@quicinc.com>
Hi Bjorn / Wim,
On Tue, Feb 24, 2026 at 02:58:05PM +0530, Pavan Kondeti wrote:
> Hi Bjorn / Wim,
>
> On Tue, Nov 18, 2025 at 10:40:55AM +0000, Hrishabh Rajput via B4 Relay wrote:
> > Gunyah is a Type-I hypervisor which was introduced in the patch series
> > [1]. It is an open source hypervisor. The source repo is available at
> > [2].
> >
> > The Gunyah Hypervisor doesn't allow its Virtual Machines to directly
> > access the MMIO watchdog. It either provides the fully emulated MMIO
> > based watchdog interface or the SMC-based watchdog interface depending
> > on the hypervisor configuration.
> > The SMC-based watchdog follows ARM's SMC Calling Convention (SMCCC)
> > version 1.1 and uses Vendor Specific Hypervisor Service Calls space.
> >
> > This patch series adds support for the SMC-based watchdog interface
> > provided by the Gunyah Hypervisor.
> >
> > This series is tested on SM8750 platform.
> >
> > [1]
> > https://lore.kernel.org/all/20240222-gunyah-v17-0-1e9da6763d38@quicinc.com/
> >
> > [2]
> > https://github.com/quic/gunyah-hypervisor
> >
> > Signed-off-by: Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>
> > ---
> > Changes in v8:
> > - Fix error handling in gunyah_wdt_probe() to fail silently with -ENODEV
> > if WDT_STATUS call returns -EOPNOTSUPP, indicating support for Gunyah
> > watchdog is not present. Fail with logs for other errors.
> > - Link to v7: https://lore.kernel.org/r/20251114-gunyah_watchdog-v7-0-f5c155b941d5@oss.qualcomm.com
> >
>
> The series applies cleanly on v7.0-rc1. I have tested the watchdog
> driver functionality and ramdumps collection on Kodiak RB3 Gen2
> platform. Can you please pick this series for v7.1?
>
> As Hrishabh mentioned earlier, both patches don't have any compile time
> dependencies.
>
Since Hrishabh has left Qualcomm, I am taking over the series. Hence
sending request emails to include this series for v7.0 . I did verify
this on v7.0-rc1 as mentioned above. Since the series applies cleanly, I
have not re-sent the series. However, if you prefer to resend it since a
new person taking over, I can re-send the series with my Signed-off-by.
Please let me know your preference.
Thanks,
Pavan
prev parent reply other threads:[~2026-03-03 5:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 10:40 Hrishabh Rajput via B4 Relay
2025-11-18 10:40 ` [PATCH v8 1/2] firmware: qcom: scm: Register gunyah watchdog device Hrishabh Rajput via B4 Relay
2025-11-18 11:18 ` Kathiravan Thirumoorthy
2025-11-18 11:32 ` Krzysztof Kozlowski
2025-11-18 11:46 ` Krzysztof Kozlowski
2025-11-18 10:40 ` [PATCH v8 2/2] watchdog: Add driver for Gunyah Watchdog Hrishabh Rajput via B4 Relay
2025-11-18 12:24 ` Dmitry Baryshkov
2025-11-19 5:18 ` Guenter Roeck
2025-12-11 13:20 ` Mukesh Ojha
2025-12-02 11:23 ` [PATCH v8 0/2] Add support " Hrishabh Rajput
2025-12-02 15:59 ` Krzysztof Kozlowski
2025-12-15 13:00 ` Hrishabh Rajput
2026-01-06 5:55 ` Pavan Kondeti
2026-01-13 6:00 ` Pavan Kondeti
2026-02-24 9:28 ` Pavan Kondeti
2026-03-03 5:23 ` Pavan Kondeti [this message]
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=4427f335-bb50-44af-94a5-142d8355a705@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=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=shivendra.pratap@oss.qualcomm.com \
--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®