linux-kernel - RE: [PATCH] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards [Klartext]

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 24 May 2021 22:38:49 +0000
From:   Christoph Niedermaier <cniedermaier@...electronics.com>
To:     'Fabio Estevam' <festevam@...il.com>
CC:     "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>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Shawn Guo <shawnguo@...nel.org>,
        kernel <kernel@...electronics.com>
Subject: RE: [PATCH] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02
 boards [Klartext]

From: Fabio Estevam <festevam@...il.com>
Sent: Monday, May 24, 2021 3:03 PM
> 
> Hi Christoph,
>

Hi Fabio,

> 
> On Mon, May 24, 2021 at 9:17 AM Christoph Niedermaier
> <cniedermaier@...electronics.com> wrote:
> 
>> +      - description: i.MX6S DHCOM DRC02 Board
>> +        items:
>> +          - const: dh,imx6s-dhcom-drc02
>> +          - const: dh,imx6s-dhcom-som
>> +          - const: fsl,imx6s
> 
> We don't have an fsl,imx6s compatible for the i.MX6 Solo variant. We
> just use fsl,imx6dl instead.

My thought was to be future proof. If there is no match with the Solo now,
it will fall back to the i.MX6 DualLite. That is why I added both fsl,imx6s
and fsl,imx6dl in this order.

Should I remove the line with fsl,imx6s?

Regards
Christoph