From: Shawn Guo <shawnguo@kernel.org>
To: Leo Li <leoyang.li@nxp.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"a.tropschug@ebs-systart.com" <a.tropschug@ebs-systart.com>,
"m.bittner@ebs-systart.com" <m.bittner@ebs-systart.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Amit Kucheria <amit.kucheria@linaro.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/3] dt-bindings: arm: fsl: Add devicetree binding for Oxalis
Date: Tue, 22 Jan 2019 11:00:12 +0800 [thread overview]
Message-ID: <20190122030011.GC19233@dragon> (raw)
In-Reply-To: <AM6PR04MB5863AE2A3DD74882BEC680CA8F9F0@AM6PR04MB5863.eurprd04.prod.outlook.com>
On Mon, Jan 21, 2019 at 07:57:20PM +0000, Leo Li wrote:
> > > So it seems the compatible of the boards below are missing there.
> > >
> > > ls1021a-moxa-uc-8410a.dts
> > > ls1021a-qds.dts
> > > ls1021a-twr.dts
> >
> > So how should we proceed here? The above mentioned boards are lacking
> > compatible in dts files and I guess that's the reason they didn't get
> > mentioned in "fsl" binding file.
> >
> > Should I just go ahead and add the compatibles for these boards and list
> > them in binding file?
>
> Please go ahead and do that. One thing is that the moxa-uc-8410a board is a 3rd-party board, not sure if it should belong to the fsl binding file.
The fsl.yaml is designed to contain various boards using fsl SoCs, so
it's fine.
Shawn
next prev parent reply other threads:[~2019-01-22 3:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 10:20 [PATCH v2 0/3] Add Oxalis board support Manivannan Sadhasivam
2019-01-14 10:20 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add EBS-SYSTART GmbH Vendor Prefix Manivannan Sadhasivam
2019-01-16 21:10 ` Rob Herring
2019-01-14 10:20 ` [PATCH v2 2/3] dt-bindings: arm: fsl: Add devicetree binding for Oxalis Manivannan Sadhasivam
2019-01-14 18:02 ` Rob Herring
2019-01-14 18:10 ` Manivannan Sadhasivam
2019-01-16 2:21 ` Shawn Guo
2019-01-16 4:07 ` Rob Herring
2019-01-16 10:14 ` Shawn Guo
2019-01-21 6:09 ` Manivannan Sadhasivam
2019-01-21 19:57 ` Leo Li
2019-01-22 3:00 ` Shawn Guo [this message]
2019-01-14 10:20 ` [PATCH v2 3/3] arm64: dts: freescale: Add devicetree " Manivannan Sadhasivam
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=20190122030011.GC19233@dragon \
--to=shawnguo@kernel.org \
--cc=a.tropschug@ebs-systart.com \
--cc=amit.kucheria@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.bittner@ebs-systart.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@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).