lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAL_JsqLvdFgiPLZoUzXXPmoff2u1pz5pcSdaCh9p=bh1+3PMSg@mail.gmail.com> Date: Thu, 14 Oct 2021 07:46:50 -0500 From: Rob Herring <robh+dt@...nel.org> To: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com> Cc: Li Yang <leoyang.li@....com>, Shawn Guo <shawnguo@...nel.org>, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" <linux-arm-kernel@...ts.infradead.org>, Michael Ellerman <mpe@...erman.id.au>, linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>, lkml <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 1/5] dt-bindings: memory: fsl: convert ifc binding to yaml schema On Mon, Oct 4, 2021 at 4:31 AM Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com> wrote: > > On 01/10/2021 18:17, Li Yang wrote: > > On Fri, Oct 1, 2021 at 5:01 AM Krzysztof Kozlowski > > <krzysztof.kozlowski@...onical.com> wrote: > >> > > (...) > > >>> + > >>> + interrupts: > >>> + minItems: 1 > >>> + maxItems: 2 > >>> + description: | > >>> + IFC may have one or two interrupts. If two interrupt specifiers are > >>> + present, the first is the "common" interrupt (CM_EVTER_STAT), and the > >>> + second is the NAND interrupt (NAND_EVTER_STAT). If there is only one, > >>> + that interrupt reports both types of event. > >>> + > >>> + little-endian: > >>> + $ref: '/schemas/types.yaml#/definitions/flag' > >> > >> type: boolean > > > > It will not have a true or false value, but only present or not. Is > > the boolean type taking care of this too? > > boolean is for a property which does not accept values and true/false > depends on its presence. > See: > Documentation/devicetree/bindings/phy/lantiq,vrx200-pcie-phy.yaml > Documentation/devicetree/bindings/thermal/qoriq-thermal.yaml They are equivalent, so either can be used. Really what is needed here is a common schema for the endianness properties defining the type once. Then any binding using a property can just do 'little-endian: true'. Rob
Powered by blists - more mailing lists