From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: andrew@codeconstruct.com.au, avifishman70@gmail.com,
tali.perry1@gmail.com, wim@linux-watchdog.org,
linux@roeck-us.net, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, venture@google.com, yuenn@google.com,
benjaminfair@google.com, joel@jms.id.au,
openbmc@lists.ozlabs.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: watchdog: Add NPCM reset status support
Date: Tue, 17 Feb 2026 08:12:42 +0100 [thread overview]
Message-ID: <52f9b04a-256a-4559-b3e6-28fe695e1b6d@kernel.org> (raw)
In-Reply-To: <CAP6Zq1gRd8zDi1rOkX+2x3WP0ZGnULaJ0cGS6bwpRpcmQNmRCA@mail.gmail.com>
On 17/02/2026 07:53, Tomer Maimon wrote:
> On Mon, 16 Feb 2026 at 20:03, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
>> On Mon, Feb 16, 2026 at 04:59:18PM +0200, Tomer Maimon wrote:
>>> On Mon, 16 Feb 2026 at 16:48, Krzysztof Kozlowski <krzk@kernel.org>
>> wrote:
>>>>>>>>> + syscon:
>>>>>>>>
>>>>>>>> First iteration. See "How to Get Your DT Schema Bindings Accepted
>> in
>>>>>>>> Less Than 10 Iterations"
>>>>>>>>
>>>>>>> Thanks, it was very helpful.
>>>>>>> the syscon property is already found in the WD node
>>>>>>> in nuvoton-common-npcm8xx.dtsi file, what should I do:
>>>>>>
>>>>>> How is that file related to this binding?
>>>>>>
>>>>>> Either you document existing ABI or you add new (for new device).
>> Commit
>>>>>> msg MUST be explicit about it and provide the reasons. If wrong
>> (e.g.
>>>>>> discouraged) ABI was already used then it depends how and when it
>> got
>>>>>> into the kernel, e.g. if someone bypassed DT completely just to get
>> it
>>>>>> inside.
>>>>>>
>>>>> The syscon property is already used in the upstream NPCM8xx DTSI
>> watchdog
>>>>> node, so I will document it as existing ABI and mark it deprecated. I
>>>> will
>>>>
>>>> And how it is used? I cannot find its usage, so I do not agree on
>>>> documenting it. Property should be removed or at least provide the
>>>> justification/impact of removal, if you need it to stay.
>>>>
>>>> Understood. The syscon phandle is used by the watchdog driver to read
>> and
>>
>> You messed up quotes.
>>
>> Can you point me to the line? I REALLY want to be sure that we are not
>> wasting each other time, e.g. me looking at wrong code or you telling me
>> some bollocks from downstream.
>>
> The syscon property is not used in the current upstream npcm_wdt driver.
> It is used *in this patch set*, which introduces the function
Why would that matter for the ABI?
So no, your buggy DTS sneaked into the kernel before submitting bindings
is not acceptable thus ABI which was NEVER reviewed must be removed.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-17 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 13:38 [PATCH v1 0/2] watchdog: npcm: Add reset status detection support Tomer Maimon
2026-02-10 13:38 ` [PATCH v1 1/2] dt-bindings: watchdog: Add NPCM reset status support Tomer Maimon
2026-02-10 16:11 ` Krzysztof Kozlowski
[not found] ` <CAP6Zq1jZorLxXQYqm5KzcYdoRzcFtD1KQqzmgaa6KKy-+Tpv+Q@mail.gmail.com>
2026-02-16 11:15 ` Krzysztof Kozlowski
[not found] ` <CAP6Zq1hLkT-xMwV99yVE-hLsf_nT+V_3v7sEshfqEkkRCkEevA@mail.gmail.com>
2026-02-16 14:48 ` Krzysztof Kozlowski
[not found] ` <CAP6Zq1iWpHc-Rsq62iBN0VtYmYS2=KhU12TE_5nxztr+HbB+tA@mail.gmail.com>
2026-02-16 18:03 ` Krzysztof Kozlowski
[not found] ` <CAP6Zq1gRd8zDi1rOkX+2x3WP0ZGnULaJ0cGS6bwpRpcmQNmRCA@mail.gmail.com>
2026-02-17 7:12 ` Krzysztof Kozlowski [this message]
2026-02-10 13:38 ` [PATCH v1 2/2] watchdog: npcm: Add " Tomer Maimon
2026-02-10 16:02 ` Guenter Roeck
[not found] ` <CAP6Zq1gGVB+hk+=xSRyPgddq07F_B+oE-dc246JRW2_waoe_bg@mail.gmail.com>
2026-02-16 15:26 ` Guenter Roeck
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=52f9b04a-256a-4559-b3e6-28fe695e1b6d@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=wim@linux-watchdog.org \
--cc=yuenn@google.com \
/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