From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>,
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>
Subject: Re: [PATCH v3] watchdog: Add driver for Gunyah Watchdog
Date: Tue, 28 Oct 2025 17:44:19 +0100 [thread overview]
Message-ID: <ccd14d85-320d-4f6b-bafb-45476ff15987@kernel.org> (raw)
In-Reply-To: <4659e69b-907a-49ba-8eb6-ac17232a5219@roeck-us.net>
On 28/10/2025 17:06, Guenter Roeck wrote:
> On 10/28/25 02:35, Hrishabh Rajput via B4 Relay wrote:
>> +
>> + ret = gunyah_wdt_call(GUNYAH_WDT_STATUS, 0, 0, &res);
>> + if (ret)
>> + return -ENODEV;
>> +
>> + ret = platform_driver_register(&gunyah_wdt_driver);
>> + if (ret)
>> + return ret;
>> +
>> + gunyah_wdt_dev = platform_device_register_simple(GUNYAH_WDT_DRV_NAME,
>> + -1, NULL, 0);
>
> I did not follow the discussion around this, so I may be missing something.
> If so, apologies.
>
> This is a highly unusual approach. What is the point of not instantiating
> the watchdog device through devicetree and doing it in the init function
> instead ? There should be a devicetree node which instantiates the device;
> it should never be instantiated from the init function unless there _is_
> no devicetree, which is obviously not the case here.
We told that to them already... Every iteration of gunyah feels like
pushing their approach without regard to community feedback.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-28 16:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 9:35 [PATCH v3] watchdog: Add driver for Gunyah Watchdog Hrishabh Rajput via B4 Relay
2025-10-28 9:40 ` Krzysztof Kozlowski
2025-10-28 10:58 ` Hrishabh Rajput
2025-10-28 11:04 ` Krzysztof Kozlowski
2025-10-28 11:07 ` Krzysztof Kozlowski
2025-10-28 12:27 ` Pavan Kondeti
2025-10-28 16:17 ` Krzysztof Kozlowski
2025-10-28 16:29 ` Krzysztof Kozlowski
2025-10-28 16:33 ` Pavan Kondeti
2025-10-28 16:39 ` Neil Armstrong
2025-10-28 17:03 ` Pavan Kondeti
2025-10-28 16:40 ` Krzysztof Kozlowski
2025-10-28 16:51 ` Dmitry Baryshkov
2025-10-28 16:53 ` Krzysztof Kozlowski
2025-10-28 17:07 ` Pavan Kondeti
2025-10-28 16:30 ` Neil Armstrong
2025-10-28 16:36 ` Pavan Kondeti
2025-10-28 16:06 ` Guenter Roeck
2025-10-28 16:40 ` Pavan Kondeti
2025-10-28 16:45 ` Krzysztof Kozlowski
2025-10-28 17:29 ` Guenter Roeck
2025-10-28 17:49 ` Pavan Kondeti
2025-10-28 16:44 ` Krzysztof Kozlowski [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=ccd14d85-320d-4f6b-bafb-45476ff15987@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=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;
as well as URLs for NNTP newsgroup(s).