From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"ext Tony Lindgren" <tony@atomide.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Kevin Hilman" <khilman@kernel.org>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Michal Simek" <michal.simek@xilinx.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>, arm-soc <arm@kernel.org>,
"Joel Stanley" <joel@jms.id.au>,
"Andy Gross" <andy.gross@linaro.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"Jason Cooper" <jason@lakedaemon.net>,
"Simon Horman" <horms@verge.net.au>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"Andreas Färber" <afaerber@suse.de>,
"Daniel Mack" <daniel@zonque.org>
Subject: Re: Moving ARM dts files
Date: Wed, 5 Dec 2018 08:34:47 +0000 [thread overview]
Message-ID: <20181205162941.2d8bbfaf@xhacker.debian> (raw)
In-Reply-To: <CACRpkdYs_s9m=fUuOcfqcvP5BMXity5GH17RSMyvHzdZ9aFNzA@mail.gmail.com>
On Wed, 5 Dec 2018 09:19:49 +0100 Linus Walleij wrote:
> On Wed, Dec 5, 2018 at 7:02 AM Jisheng Zhang wrote:
> > Rob Herring wrote:
>
> > > 'armada' : 'marvell',
> > > 'berlin' : 'marvell',
> >
> > Now, berlin SoC is synaptics' SoC ;)
>
> This illustrates perfectly the artificial nature of using vendor names
> as prefixes with DT properties, prefix names, directories etc.
>
> Companies start out purporting to be some eternal entity and the
> next day they buy each other left and right and license their
> hardware IP to whoever wants it.
>
> It actually makes much more sense to organize these files by
> the SoC family name, because that doesn't change when the
> SoC is sold to another company.
If the SoC is sold to another company, then
case1: The original SoC family is renamed to another family.
case2: Based on the original SoC, a newer SoC family comes out.
I'm not sure it's still fine to put the new or renamed SoCs' files into the
original SoC directory.
Another issue is: who will be the maintainer of new or renamed SoC family?
Thanks,
Jisheng
>
> omap/* containing all OMAP platforms, msm/* for all Qualcomm
> SoCs etc. SoC names/codenames are at least eternal once they
> have been manufactured and we can keep them together
> no matter what vendor currently controls it.
>
> However I think there was a fork in the road ages ago when
> someone or something decided to use vendor prefixes for
> DT properties leading to this situation that we can no longer
> back out of.
>
> It has the side effect of splitting DTS files with the same SoC
> in two different folders marvell/* and synaptics/*
> it's a bit meh.
>
> Yours,
> Linus Walleij
_______________________________________________
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:[~2018-12-05 8:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 18:36 Moving ARM dts files Rob Herring
2018-12-04 18:47 ` Alexandre Belloni
2018-12-04 19:09 ` Rob Herring
2018-12-04 22:21 ` Simon Horman
2018-12-05 1:22 ` Andreas Färber
2018-12-05 4:17 ` Rob Herring
2018-12-05 17:33 ` Tom Rini
2018-12-06 13:32 ` Andreas Färber
2018-12-06 19:06 ` Rob Herring
2018-12-06 20:06 ` Mark Brown
2018-12-06 20:49 ` Olof Johansson
2018-12-07 14:57 ` Rob Herring
2018-12-07 15:16 ` Mark Brown
2018-12-07 15:29 ` Rob Herring
2018-12-06 20:14 ` Tom Rini
2018-12-05 4:18 ` Masahiro Yamada
2018-12-05 9:48 ` Michal Simek
2018-12-05 6:02 ` Jisheng Zhang
2018-12-05 8:19 ` Linus Walleij
2018-12-05 8:34 ` Jisheng Zhang [this message]
2018-12-05 9:04 ` Linus Walleij
2018-12-05 15:01 ` Rob Herring
2018-12-05 21:03 ` Linus Walleij
2018-12-06 13:39 ` Uwe Kleine-König
2018-12-06 13:58 ` Rob Herring
2018-12-06 14:05 ` Alexandre Belloni
2018-12-06 14:30 ` Linus Walleij
2018-12-06 16:57 ` Rob Herring
2018-12-06 22:12 ` Linus Walleij
2018-12-07 23:35 ` Tony Lindgren
2018-12-05 8:13 ` Nicolas.Ferre
2018-12-05 15:14 ` Neil Armstrong
2018-12-05 17:36 ` Li Yang
2018-12-07 22:33 ` Rob Herring
2018-12-08 9:25 ` Krzysztof Kozlowski
2018-12-08 22:40 ` Linus Walleij
2018-12-11 15:58 ` Olof Johansson
2018-12-08 10:07 ` Ian Campbell
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=20181205162941.2d8bbfaf@xhacker.debian \
--to=jisheng.zhang@synaptics.com \
--cc=afaerber@suse.de \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=andy.gross@linaro.org \
--cc=arm@kernel.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=horms@verge.net.au \
--cc=jason@lakedaemon.net \
--cc=joel@jms.id.au \
--cc=khilman@kernel.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=yamada.masahiro@socionext.com \
/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).