From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: dts: add initial support for TBS2910 Matrix ARM mini PC
Date: Tue, 21 Oct 2014 16:17:02 +0200 [thread overview]
Message-ID: <20141021141702.GQ14443@pengutronix.de> (raw)
In-Reply-To: <54464BA7.9030001@gmail.com>
On Tue, Oct 21, 2014 at 02:03:51PM +0200, Sebastian Hesselbarth wrote:
> On 21.10.2014 13:57, S?ren Moch wrote:
> >>>+/ {
> >>>+ model = "TBS2910 Matrix ARM mini PC";
> >>>+ compatible = "tbs,imx6q-tbs2910", "fsl,imx6q";
> >>
> >>[...]
> >>Also, board compatible should only be "tbs,tbs2910".
> >
> >Similar boards use e.g.
> > compatible = "fsl,imx6q-sabresd", "fsl,imx6q";
> > compatible = "udoo,imx6q-udoo", "fsl,imx6q";
> > compatible = "wand,imx6q-wandboard", "fsl,imx6q";
> >
> >So is it really better to use only "tbs,tbs2910" here?
>
> Hmm, having the SoC name again in the board compatible seems
> odd to me, e.g. we have "google,chromecast" without the SoC
> name in it.
No. My vanilla 3.17 kernel has this:
arch/arm/boot/dts/berlin2cd-google-chromecast.dts:17: compatible = "google,chromecast", "marvell,berlin2cd", "marvell,berlin";
>
> Anyway, it is just a compatible and if it is common for imx-
> based boards or Shawn/Sascha like to have it this way you
> should stick with that, of course.
It has to be that way, because the kernel matches to "marvell,berlin",
not the board name. Otherwise we would have to compile in all board
compatible strings into the kernel or the kernel would refuse to start.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2014-10-21 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 12:27 [PATCH] arm: dts: add initial support for TBS2910 Matrix ARM mini PC Soeren Moch
2014-10-21 7:40 ` Sebastian Hesselbarth
2014-10-21 11:57 ` Sören Moch
2014-10-21 12:03 ` Sebastian Hesselbarth
2014-10-21 14:17 ` Sascha Hauer [this message]
2014-10-21 18:25 ` Sebastian Hesselbarth
2014-10-21 20:23 ` [PATCH v2] " Soeren Moch
2014-10-25 15:33 ` Shawn Guo
2014-10-25 17:50 ` Soeren Moch
2014-10-25 18:51 ` Sebastian Hesselbarth
2014-10-26 0:15 ` Shawn Guo
2014-10-26 0:55 ` Shawn Guo
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=20141021141702.GQ14443@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).