Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	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>
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 12:07:40 +0100	[thread overview]
Message-ID: <636a1f99-acd4-4904-8fae-f159646cc1a0@kernel.org> (raw)
In-Reply-To: <73955d58-544c-4299-a099-bfd9e5912a40@kernel.org>

On 28/10/2025 12:04, Krzysztof Kozlowski wrote:
> On 28/10/2025 11:58, Hrishabh Rajput wrote:
>>
>> On 10/28/2025 3:10 PM, Krzysztof Kozlowski wrote:
>>> On 28/10/2025 10:35, Hrishabh Rajput via B4 Relay wrote:
>>>> +
>>>> +static int __init gunyah_wdt_init(void)
>>>> +{
>>>> +	struct arm_smccc_res res;
>>>> +	struct device_node *np;
>>>> +	int ret;
>>>> +
>>>> +	/* Check if we're running on a Qualcomm device */
>>>> +	np = of_find_compatible_node(NULL, NULL, "qcom,smem");
>>> I don't think you implemented my feedback. This again is executed on
>>> every platform, e.g. on Samsung, pointlessly.
>>>
>>> Implement previous feedback.
>>
>> Do you want us to add platform device from another driver which is 
>> probed only on Qualcomm devices (like socinfo from previous discussion) 
>> and get rid of the module init function entirely? As keeping anything in 
>> the module init will get it executed on all platforms.
> 
> Instead of asking the same can you read previous discussion? What is
> unclear here:
> https://lore.kernel.org/all/3b901f9d-dbfa-4f93-a8d2-3e89bd9783c9@kernel.org/
> ?
> 
>>
>>
>> With this patch version, we have tried to reduce the code execution on 
>> non-Qualcomm devices (also tried the alternative as mentioned in the 
>> cover letter). Adding platform device from another driver as described 
>> above would eliminate it entirely, please let us know if you want us to 
>> do that.
> 
> Why do I need to repeat the same as last time?


Now I see that you completely ignored previous discussion and sent THE
SAME approach.

NAK. It is waste of our time if you keep ignoring reviewers and force us
to re-iterate the same over and over again.

Best regards,
Krzysztof

  reply	other threads:[~2025-10-28 11:07 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 [this message]
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

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=636a1f99-acd4-4904-8fae-f159646cc1a0@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