[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240213-estranged-charger-bf0372f367e0@spud>
Date: Tue, 13 Feb 2024 19:13:57 +0000
From: Conor Dooley <conor@...nel.org>
To: Dharma.B@...rochip.com
Cc: robh@...nel.org, tglx@...utronix.de, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, Nicolas.Ferre@...rochip.com,
alexandre.belloni@...tlin.com, claudiu.beznea@...on.dev,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] dt-bindings: interrupt-controller: Convert Atmel AIC
to json-schema
On Tue, Feb 13, 2024 at 04:23:36AM +0000, Dharma.B@...rochip.com wrote:
> On 12/02/24 7:38 pm, Rob Herring wrote:
> > On Fri, Feb 09, 2024 at 03:31:22PM +0530, Dharma Balasubiramani wrote:
> >> + atmel,external-irqs:
> >> + $ref: /schemas/types.yaml#/definitions/uint32-array
> >> + description: u32 array of external irqs.
> >
> > Constraints on the array size and/or entry values?
>
> The hardware's support for external IRQs may differ, which is why a u32
> array is utilized. This choice is based on the fact that IRQ numbers are
> commonly expressed as integers, and a 32-bit unsigned integer provides a
> standardized size capable of representing a broad range of numbers. This
> size is more than adequate for accommodating IRQ numbering.
I don't think Rob was questioning your use of u32s, but rather the fact
that you do not limit the values at all nor the number of values.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists