From: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Antony Pavlov <antonynpavlov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Frank Rowand
<frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>,
feedback-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org
Subject: Re: RFC: board dts-file naming scheme
Date: Tue, 16 Aug 2016 11:43:40 -0500 [thread overview]
Message-ID: <CAL_JsqJqY4GFrUfwudN4BP7ph9s7R78aof_YiEC-GDbS12U2_Q@mail.gmail.com> (raw)
In-Reply-To: <20160816181321.d90e979cae6c7b5d0959b381-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Tue, Aug 16, 2016 at 10:13 AM, Antony Pavlov <antonynpavlov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi all!
>
> I have not found any recomendation on board dts-file naming scheme
> in linux.git/Documentation/devicetree/.
>
> ARM/ARM64 Linux mostly uses <soc-name>-<board-name>.dts board dts-file
> naming scheme (also see slide "Adding the support for a new ARM board" from [1]).
>
> arch/arm/boot/dts/am335x-baltos-ir5221.dts
> arch/arm/boot/dts/at91-ariag25.dts
> arch/arm/boot/dts/exynos5250-arndale.dts
> arch/arm/boot/dts/imx6dl-gw54xx.dts
> arch/arm/boot/dts/sun9i-a80-cubieboard4.dts
> arch/arm/boot/dts/tegra30-colibri-eval-v3.dts
> arm64/boot/dts/qcom/apq8016-sbc.dts
> arm64/boot/dts/cavium/thunder-88xx.dts
> arm64/boot/dts/broadcom/ns2-svk.dts
> arm64/boot/dts/rockchip/rk3368-r88.dts
> arm64/boot/dts/mediatek/mt8173-evb.dts
>
> MIPS Linux mostly uses <soc-name>_<board-name>.dts naming scheme:
>
> arch/mips/boot/dts/netlogic/xlp_gvp.dts
> arch/mips/boot/dts/qca/ar9132_tl_wr1043nd_v1.dts
> arch/mips/boot/dts/ralink/mt7620a_eval.dts
>
> Can we elaborate some common rule on board dts-file naming scheme
> and add it into linux.git/Documentation/devicetree/?
My guidance is follow what most other files in a given directory do.
In absence of that, use '-'.
If you want to add documentation, then I'll take it. I can tell you
that arm-soc maintainers are not going to take renames for things that
don't follow the documentation.
Rob
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-08-16 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 15:13 RFC: board dts-file naming scheme Antony Pavlov
[not found] ` <20160816181321.d90e979cae6c7b5d0959b381-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-16 16:43 ` Rob Herring [this message]
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_JsqJqY4GFrUfwudN4BP7ph9s7R78aof_YiEC-GDbS12U2_Q@mail.gmail.com \
--to=robh+dt-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=antonynpavlov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=feedback-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=marex-ynQEQJNshbs@public.gmane.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).