[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJyZt=VCv2bX1YYFQt91BcFqDWfeAqkJVcF7eFD0_JM1g@mail.gmail.com>
Date: Tue, 8 Jan 2019 08:56:49 -0600
From: Rob Herring <robh@...nel.org>
To: Vokáč Michal <Michal.Vokac@...ft.com>
Cc: Shawn Guo <shawnguo@...nel.org>,
Fabio Estevam <fabio.estevam@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Andrew Lunn <andrew@...n.ch>
Subject: Re: [PATCH v2] ARM: dts: imx: Add Y Soft IOTA Draco, Hydra and Ursa boards
On Tue, Jan 8, 2019 at 5:43 AM Vokáč Michal <Michal.Vokac@...ft.com> wrote:
>
> On 29.12.2018 00:25, Rob Herring wrote:
> > On Tue, Dec 18, 2018 at 02:42:11PM +0000, Vokáč Michal wrote:
> >> These are i.MX6S/DL based SBCs embedded in various Y Soft products.
> >> All share the same board design but have slightly different HW
> >> configuration.
[...]
> >> +/ {
> >> + model = "Y Soft IOTA Draco i.MX6Solo board";
> >> + compatible = "ysoft,imx6dl-yapp4-draco", "fsl,imx6dl";
> >
> > All compatible strings should be documented, not just SoC vendor boards.
>
> OK, I will add a Documentation/devicetree/bindings/arm/ysoft.yaml file for that.
Actually, it should go in fsl.yaml. The file for every board vendor is
gone. i.MX was pretty much the only platform doing that.
Rob
Powered by blists - more mailing lists