[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7fc3b50b-c9fc-b1b5-ba84-752b2e3da7d7@microchip.com>
Date: Mon, 4 Jul 2022 13:24:54 +0000
From: <Tudor.Ambarus@...rochip.com>
To: <Sergiu.Moga@...rochip.com>, <broonie@...nel.org>,
<robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
<Nicolas.Ferre@...rochip.com>, <alexandre.belloni@...tlin.com>,
<Claudiu.Beznea@...rochip.com>
CC: <linux-spi@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <Kavyasree.Kotagiri@...rochip.com>,
<UNGLinuxDriver@...rochip.com>
Subject: Re: [PATCH v2] spi: atmel: convert spi_atmel to json-schema
On 7/4/22 11:31, Sergiu Moga wrote:
> + atmel,fifo-size:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Maximum number of data the RX and TX FIFOs can store for FIFO
> + capable SPI controllers.
> + minimum: 16
> + maximum: 32
Shouldn't we have an enum instead of a range? Can the FIFO size have a value of 24?
Powered by blists - more mailing lists