[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221118141458.954646-1-michael@walle.cc>
Date: Fri, 18 Nov 2022 15:14:58 +0100
From: Michael Walle <michael@...le.cc>
To: tudor.ambarus@...rochip.com
Cc: alexandre.belloni@...tlin.com, broonie@...nel.org,
claudiu.beznea@...rochip.com, devicetree@...r.kernel.org,
krzysztof.kozlowski+dt@...aro.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mtd@...ts.infradead.org, linux-spi@...r.kernel.org,
nicolas.ferre@...rochip.com, robh+dt@...nel.org
Subject: Re: [PATCH 1/8] spi: dt-bindings: Introduce spi-cs-setup-ns property
From: Tudor Ambarus <tudor.ambarus@...rochip.com>
> diff --git a/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml b/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml
> index dca677f9e1b9..ead2cccf658f 100644
> --- a/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml
> +++ b/Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml
> @@ -44,6 +44,11 @@ properties:
> description:
> Maximum SPI clocking speed of the device in Hz.
>
> + spi-cs-setup-ns:
> + description:
> + Delay in nanosecods to be introduced by the controller after CS is
> + asserted.
> +
Does this need a type as the spi-cs-setup-ns is apparently just 16bit? At
least the driver uses it that way.
But IMHO this should just be a normal uint32 value to be consistent with
all the other properties. Also the max value with 16bit will be 'just'
65us.
-michael
Powered by blists - more mailing lists