From: Rob Herring <robh@kernel.org>
To: "Vokáč Michal" <Michal.Vokac@ysoft.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v2] ARM: dts: imx: Add Y Soft IOTA Draco, Hydra and Ursa boards
Date: Tue, 8 Jan 2019 08:56:49 -0600 [thread overview]
Message-ID: <CAL_JsqJyZt=VCv2bX1YYFQt91BcFqDWfeAqkJVcF7eFD0_JM1g@mail.gmail.com> (raw)
In-Reply-To: <49371bd4-6ab9-31c3-dd48-800becac17e3@ysoft.com>
On Tue, Jan 8, 2019 at 5:43 AM Vokáč Michal <Michal.Vokac@ysoft.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
next prev parent reply other threads:[~2019-01-08 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 14:42 [PATCH v2] ARM: dts: imx: Add Y Soft IOTA Draco, Hydra and Ursa boards Vokáč Michal
2018-12-28 18:20 ` Fabio Estevam
2019-01-08 11:40 ` Vokáč Michal
2018-12-28 23:25 ` Rob Herring
2019-01-08 11:43 ` Vokáč Michal
2019-01-08 14:25 ` Vokáč Michal
2019-01-08 14:53 ` Rob Herring
2019-01-08 14:56 ` Rob Herring [this message]
2019-01-08 15:00 ` Vokáč Michal
2019-01-08 16:09 ` Vokáč Michal
2019-01-08 18:11 ` Rob Herring
2019-01-10 13:57 ` Shawn Guo
2019-01-10 14:06 ` Vokáč Michal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL_JsqJyZt=VCv2bX1YYFQt91BcFqDWfeAqkJVcF7eFD0_JM1g@mail.gmail.com' \
--to=robh@kernel.org \
--cc=Michal.Vokac@ysoft.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).