[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200312211102.GA21647@bogus>
Date: Thu, 12 Mar 2020 16:11:02 -0500
From: Rob Herring <robh@...nel.org>
To: Sergey.Semin@...kalelectronics.ru
Cc: Lee Jones <lee.jones@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Serge Semin <fancer.lancer@...il.com>,
Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Paul Burton <paulburton@...nel.org>,
Ralf Baechle <ralf@...ux-mips.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: syscon: Add syscon endian properties
support
On Fri, Mar 06, 2020 at 04:03:38PM +0300, Sergey.Semin@...kalelectronics.ru wrote:
> From: Serge Semin <Sergey.Semin@...kalelectronics.ru>
>
> In accordance with the syscon-driver (drivers/mfd/syscon.c) the syscon
> dts-nodes may accept endian properties of the boolean type: little-endian,
> big-endian, native-endian. Lets make sure that syscon bindings json-schema
> also supports them.
>
> Signed-off-by: Serge Semin <Sergey.Semin@...kalelectronics.ru>
> Signed-off-by: Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>
> Cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
> Cc: Paul Burton <paulburton@...nel.org>
> Cc: Ralf Baechle <ralf@...ux-mips.org>
> ---
> Documentation/devicetree/bindings/mfd/syscon.yaml | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml
> index 39375e4313d2..9ee404991533 100644
> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml
> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml
> @@ -61,6 +61,11 @@ properties:
> description:
> Reference to a phandle of a hardware spinlock provider node.
>
> +patternProperties:
> + "^(big|little|native)-endian$":
> + $ref: /schemas/types.yaml#/definitions/flag
> + description: Bytes order of the system controller memory space.
Common properties should have a type definition in a common schema. For
this one, I'd like it in the core schema in dtschema.
I'd expect for any specific 'syscon', either none or only a subset of
these are valid, so I don't think this should be added here.
Rob
Powered by blists - more mailing lists