On 13/02/2026 02:22, Shawn Guo wrote: > On Wed, Dec 24, 2025 at 09:34:30AM +0100, Krzysztof Kozlowski wrote: >>> the interrupt for soccp is defined as >>> "wdog","fatal","ready","handover","stop-ack","pong","wake-ack" >>> while other pas could be: >>> "wdog","fatal","ready","handover","stop-ack","shutdown-ack" >>> >>> so grow existing list is not work for this, >>> >>> In the v1, got your comments to adjust pas-common.yaml for the interrupt: >>> https://lore.kernel.org/all/[email protected]/ >>> >>> and in v2, interrupt are moved as part to the "allOf" with if-else and >>> also got NAK: >>> https://lore.kernel.org/all/20251030-venomous-apricot-falcon-b3fd64@kuoka/ >>> >>> Could you please share a example for us to understand how to maintain it in >>> pas-common.yaml, not define if-else and has strict order at the same time? >>> That will be very helpful. > > I guess something like this would work? > > interrupt-names: > minItems: 5 > maxItems: 7 > oneOf: > - items: > - const: wdog > - const: fatal > - const: ready > - const: handover > - const: stop-ack > - const: shutdown-ack > - items: > - const: wdog > - const: fatal > - const: ready > - const: handover > - const: stop-ack > - const: pong > - const: wake-ack
This is good for pas-common, but you also need in the same commit update all schemas having $ref to pas-common to have explicit list. For example milos has six elements and your change would basically allow the sixth item to be pong. Also several files need maxItems for interrupts, since the upper limit is now 7. Best regards, Krzysztof
