From: "Vokáč Michal" <Michal.Vokac@ysoft.com>
To: Rob Herring <robh@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] ARM: dts: imx: Add Y Soft IOTA Draco, Hydra and Ursa boards
Date: Tue, 8 Jan 2019 15:00:31 +0000 [thread overview]
Message-ID: <6fd5ac6a-edb5-a600-3c10-b46a1c1d9906@ysoft.com> (raw)
In-Reply-To: <CAL_JsqJyZt=VCv2bX1YYFQt91BcFqDWfeAqkJVcF7eFD0_JM1g@mail.gmail.com>
On 8.1.2019 15:56, Rob Herring wrote:
> 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.
OK, I will do so. Thank you.
Michal
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-08 15:00 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
2019-01-08 15:00 ` Vokáč Michal [this message]
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=6fd5ac6a-edb5-a600-3c10-b46a1c1d9906@ysoft.com \
--to=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=robh@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