[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <17daf0f387dff8145559df6a983b0a222c100514.camel@pengutronix.de>
Date: Tue, 10 Aug 2021 17:14:17 +0200
From: Jan Lübbe <jlu@...gutronix.de>
To: Joakim Zhang <qiangqing.zhang@....com>,
srinivas.kandagatla@...aro.org, robh+dt@...nel.org,
shawnguo@...nel.org
Cc: devicetree@...r.kernel.org, linux-imx@....com,
kernel@...gutronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V1 1/4] bindings: nvmem: introduce "reverse-data"
property
On Tue, 2021-08-10 at 15:35 +0800, Joakim Zhang wrote:
> Introduce "reverse-data" property for nvmem provider to reverse buffer.
>
> Signed-off-by: Joakim Zhang <qiangqing.zhang@....com>
> ---
> Documentation/devicetree/bindings/nvmem/nvmem.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/nvmem.yaml b/Documentation/devicetree/bindings/nvmem/nvmem.yaml
> index b8dc3d2b6e92..bc745083fc64 100644
> --- a/Documentation/devicetree/bindings/nvmem/nvmem.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/nvmem.yaml
> @@ -61,6 +61,11 @@ patternProperties:
> description:
> Size in bit within the address range specified by reg.
>
> + reverse-data:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description:
> + Reverse the data that read from the storage device.
I'd prefer if it was more explicit that the *bytes* will be reversed. Otherwise
a reader might think that this is reversing on the *bit* level.
Jan
> +
> required:
> - reg
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists