From: Pavan Kondeti <pavan.kondeti@oss.qualcomm.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Pavan Kondeti <pavan.kondeti@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org,
Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>,
Shivendra Pratap <shivendra.pratap@oss.qualcomm.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH RESEND v8 2/2] watchdog: Add driver for Gunyah Watchdog
Date: Tue, 5 May 2026 08:56:25 +0530 [thread overview]
Message-ID: <38fbf5da-abdd-4951-90d2-941f7cd62299@quicinc.com> (raw)
In-Reply-To: <f2386cf2-c790-4ce4-91ab-115a29399e25@roeck-us.net>
On Thu, Apr 30, 2026 at 07:37:12AM -0700, Guenter Roeck wrote:
> On 4/29/26 23:15, Pavan Kondeti wrote:
> > On Mon, Mar 30, 2026 at 09:11:48AM -0500, Bjorn Andersson wrote:
> > > On Wed, Mar 11, 2026 at 11:16:31AM +0530, Pavankumar Kondeti wrote:
> > > > From: Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>
> > > >
> > > > On Qualcomm SoCs running under the Gunyah hypervisor, access to watchdog
> > > > through MMIO is not available on all platforms. Depending on the
> > > > hypervisor configuration, the watchdog is either fully emulated or
> > > > exposed via ARM's SMC Calling Conventions (SMCCC) through the Vendor
> > > > Specific Hypervisor Service Calls space.
> > > >
> > > > Add driver to support the SMC-based watchdog provided by the Gunyah
> > > > Hypervisor. Device registration is done in the QCOM SCM driver after
> > > > checks to restrict the watchdog initialization to Qualcomm devices
> > > > running under Gunyah.
> > > >
> > > > Gunyah watchdog is not a hardware but an SMC-based vendor-specific
> > > > hypervisor interface provided by the Gunyah hypervisor. The design
> > > > involving QCOM SCM driver for registering the platform device has been
> > > > devised to avoid adding non-hardware nodes to devicetree.
> > > >
> > > > Tested-by: Shivendra Pratap <shivendra.pratap@oss.qualcomm.com>
> > > > Tested-by: Neil Armstrong <neil.armstrong@linaro.org>
> > > > Tested-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
> > > > Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> > > > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> > > > Signed-off-by: Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>
> > > > Signed-off-by: Pavankumar Kondeti <pavan.kondeti@oss.qualcomm.com>
> > >
> > > Guenter, there's no build-time dependency between the two patches. I'm
> > > applying patch 1 through the qcom tree, please apply this patch through
> > > the watchdog tree.
> > >
> > Thanks Bjorn. I noticed that 1/2 is available in v7.1-rc1 , however 2/2
> > is missing. Guenter, can you please pick it up for next release?
> >
>
> I don't send watchdog patches upstream; that has always been handled by Wim.
>
> Guenter
>
>
Thanks Guenter for the reply.
Wim,
Can you please include this driver (2/2 PATCH) for the next release? Please let us
know if I need to do anything else?
Thanks,
Pavan
next prev parent reply other threads:[~2026-05-05 3:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 5:46 [PATCH RESEND v8 0/2] Add support " Pavankumar Kondeti
2026-03-11 5:46 ` [PATCH RESEND v8 1/2] firmware: qcom: scm: Register gunyah watchdog device Pavankumar Kondeti
2026-03-11 6:50 ` Mukesh Ojha
2026-03-11 5:46 ` [PATCH RESEND v8 2/2] watchdog: Add driver for Gunyah Watchdog Pavankumar Kondeti
2026-03-30 14:11 ` Bjorn Andersson
2026-04-30 6:15 ` Pavan Kondeti
2026-04-30 14:37 ` Guenter Roeck
2026-05-05 3:26 ` Pavan Kondeti [this message]
2026-05-05 4:03 ` Kathiravan Thirumoorthy
2026-03-30 16:01 ` [PATCH RESEND v8 0/2] Add support " 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=38fbf5da-abdd-4951-90d2-941f7cd62299@quicinc.com \
--to=pavan.kondeti@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=hrishabh.rajput@oss.qualcomm.com \
--cc=konradybcio@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=mukesh.ojha@oss.qualcomm.com \
--cc=neil.armstrong@linaro.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®