[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <094855d6-a99b-4ca5-bc8f-ab6faccfd332@kernel.org>
Date: Tue, 8 Apr 2025 10:21:49 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>, wim@...ux-watchdog.org
Cc: linux@...ck-us.net, linux-watchdog@...r.kernel.org,
linux-kernel@...r.kernel.org, S32@....com, ghennadi.procopciuc@....com,
thomas.fossati@...aro.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: watchdog: Add NXP Software Watchdog
Timer
On 07/04/2025 18:03, Daniel Lezcano wrote:
> +
> +allOf:
> + - $ref: watchdog.yaml#
> +
> +properties:
> + compatible:
> + oneOf:
> + - const: nxp,s32g2-swt
> + - items:
> + - const: nxp,s32g3-swt
> + - const: nxp,s32g2-swt
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: Counter clock
> + - description: Module clock
> + - description: Register clock
> + minItems: 1
Why clocks are flexible? The SoC does not change between boards. It
should be a fixed list - block receives that number of clocks or does
not... unless you meant that different instances of the block have
different clocks?
Best regards,
Krzysztof
Powered by blists - more mailing lists