From: Rob Herring <robh+dt@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Olof Johansson <olof@lixom.net>,
Christian Marangi <ansuelsmth@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-actions@lists.infradead.org,
linux-sunxi@lists.linux.dev,
Linux-OMAP <linux-omap@vger.kernel.org>,
linux-amlogic@lists.infradead.org, linux-arm-kernel@axis.com,
linux-aspeed@lists.ozlabs.org,
linux-rpi-kernel@lists.infradead.org,
chrome-platform@lists.linux.dev,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
linux-samsung-soc@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
kernel@dh-electronics.com, linux-mediatek@lists.infradead.org,
openbmc@lists.ozlabs.org, linux-tegra@vger.kernel.org,
"linux-oxnas@groups.io" <linux-oxnas@groups.io>,
linux-arm-msm@vger.kernel.org, linux-unisoc@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-realtek-soc@lists.infradead.org
Subject: Re: [RFC PATCH 0/1] Categorize ARM dts directory
Date: Tue, 2 May 2023 20:04:17 -0500 [thread overview]
Message-ID: <CAL_JsqKRcMSijAdiP_BpyBGRuMhscZ12QFcLBAeZ+TcaQg7r4g@mail.gmail.com> (raw)
In-Reply-To: <d4b52074-d11c-4c7a-ad74-b2fce64c6d30@gmail.com>
On Tue, May 2, 2023 at 6:02 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>
> On 5/2/23 12:40, Rob Herring wrote:
> > On Tue, May 2, 2023 at 3:15 AM Arnd Bergmann <arnd@arndb.de> wrote:
> >>
> >> On Tue, Apr 25, 2023, at 17:57, Rob Herring wrote:
> >>> On Tue, Apr 25, 2023 at 2:28 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >>>
> >>>> Does your script also cater for .dts files not matching any pattern,
> >>>> but including a .dtsi file that does match a pattern?
> >>>
> >>> I assume I built everything after moving, but maybe not...
> >>>
> >>> That's all just "details". First, we need agreement on a) moving
> >>> things to subdirs and b) doing it 1-by-1 or all at once. So far we've
> >>> been stuck on a) for being 'too much churn'.
> >>
> >> Sorry for missing most of the discussion last week. The script sounds
> >> fine to me, the only reason I didn't want to do this in the past is that
> >> we had the plan to move platforms out of the kernel tree to an external
> >> repository and I wanted to do this platform at a time and also only move
> >> each one once. I don't think that is going to happen anytime soon now,
> >> so let's just do your script.
> >>
> >> Can you send me the script and/or a pull request of the resulting
> >> tree based on my soc/dt branch? Everything is merged upstream,
> >> and I think git-merge would handle the remaining merges with any
> >> other changes in mainline.
> >
> > I've dusted off my script and made a branch[1] with the result.
> > There's just a couple of fixes needed after the script is run (see the
> > top commit). The cross arch includes are all fixed up by the script.
> > dtbs_install maintains a flat install. I compared the number of .dtbs
> > before and after to check the script.
> >
> > I think the only issue remaining is finalizing the mapping of
> > platforms to subdirs. What I have currently is a mixture of SoC
> > families and vendors. The most notable are all the Freescale/NXP
> > platforms, pxa, socfpga, and stm32. It's not consistent with arm64
> > either. Once that's finalized, I still need to go update MAINTAINERS.
> >
> > Here's the current mapping:
> >
> > vendor_map = {
> > 'alphascale' : 'alphascale',
> > 'alpine' : 'alpine',
> > 'artpec' : 'axis',
> > 'axm' : 'lsi',
> > 'cx9' : 'cnxt',
> > 'ecx' : 'calxeda',
> > 'highbank' : 'calxeda',
> > 'ep7' : 'cirrus',
> > 'mxs': 'mxs',
> > 'imx23': 'mxs',
> > 'imx28': 'mxs',
> > 'sun' : 'allwinner',
> > 'imx': 'imx',
> > 'e6' : 'imx',
> > 'e7' : 'imx',
> > 'mba6' : 'imx',
> > 'ls': 'fsl',
> > 'vf': 'fsl',
> > 'qcom': 'qcom',
> > 'am3' : 'ti',
> > 'am4' : 'ti',
> > 'am5' : 'ti',
> > 'dra' : 'ti',
> > 'keystone' : 'ti',
> > 'omap' : 'ti',
> > 'compulab' : 'ti',
> > 'logicpd' : 'ti',
> > 'elpida' : 'ti',
> > 'motorola' : 'ti',
> > 'twl' : 'ti',
> > 'da' : 'ti',
> > 'dm' : 'ti',
> > 'nspire' : 'nspire',
> > 'armada' : 'marvell',
> > 'dove' : 'marvell',
> > 'kirkwood' : 'marvell',
> > 'orion' : 'marvell',
> > 'mvebu' : 'marvell',
> > 'mmp' : 'marvell',
> > 'berlin' : 'berlin',
> > 'pxa2' : 'pxa',
> > 'pxa3' : 'pxa',
> > 'pxa' : 'marvell',
> > 'arm-' : 'arm',
> > 'integ' : 'arm',
> > 'mps' : 'arm',
> > 've' : 'arm',
> > 'aspeed' : 'aspeed',
> > 'ast2' : 'aspeed',
> > 'facebook' : 'aspeed',
> > 'ibm' : 'aspeed',
> > 'openbmc' : 'aspeed',
> > 'en7' : 'airoha',
> > 'at91' : 'microchip',
> > 'sama' : 'microchip',
> > 'sam9' : 'microchip',
> > 'usb_' : 'microchip',
> > 'tny_' : 'microchip',
> > 'mpa1600' : 'microchip',
> > 'animeo_ip' : 'microchip',
> > 'aks-cdu' : 'microchip',
> > 'ethernut5' : 'microchip',
> > 'evk-pro3' : 'microchip',
> > 'pm9g45' : 'microchip',
> > 'ge86' : 'microchip',
> > 'bcm' : 'brcm',
>
> How about we use 'broadcom' here, to follow what arm64 does? I could
> rename arch/mips/boot/dts/brcm to arch/mips/boot/dts/broadcom for
> consistency, too?
Okay, though if starting clean I'd somewhat prefer to use the vendor
prefix. I guess since arm and arm64 share dtsi files, they should
match.
Rob
next prev parent reply other threads:[~2023-05-03 1:04 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 0:09 [RFC PATCH 0/1] Categorize ARM dts directory Ansuel Smith
2022-03-28 0:09 ` [RFC PATCH 1/1] ARM/arm64: categorize dts in arm dir and fix dependency in arm64 Ansuel Smith
2022-03-28 7:57 ` [PATCH RFC " Geert Uytterhoeven
2022-03-28 8:28 ` [RFC PATCH " Jesper Nilsson
2022-03-28 11:55 ` Ansuel Smith
2022-03-28 9:09 ` [Linux-stm32] " Patrice CHOTARD
2022-03-28 9:20 ` Patrice CHOTARD
2022-03-28 11:59 ` Ansuel Smith
2022-03-28 12:11 ` Patrice CHOTARD
2022-03-28 10:47 ` Matthias Brugger
2022-03-28 11:54 ` Ansuel Smith
2022-03-29 13:03 ` Romain Perier
2022-03-28 8:55 ` [RFC PATCH 0/1] Categorize ARM dts directory Daniel Palmer
2022-03-29 7:53 ` Tony Lindgren
2022-03-29 8:32 ` Andrew Jeffery
2022-03-29 9:04 ` Geert Uytterhoeven
2022-03-29 9:54 ` Tony Lindgren
2022-03-29 10:06 ` Matthias Brugger
2022-03-29 8:50 ` Nicolas Ferre
2023-04-25 16:21 ` Robin Murphy
2023-05-02 19:01 ` Rob Herring
2022-03-28 13:21 ` Jonathan Neuschäfer
2022-03-28 13:27 ` Ansuel Smith
2022-03-28 13:35 ` Jonathan Neuschäfer
2022-03-28 13:50 ` H. Nikolaus Schaller
2022-03-29 0:23 ` Andrew Jeffery
2022-03-28 14:00 ` (EXT) " Alexander Stein
2022-03-29 9:19 ` Alexandre Belloni
2022-03-29 13:20 ` Krzysztof Kozlowski
2022-03-29 4:56 ` Ansuel Smith
2023-04-24 22:10 ` Rob Herring
2023-04-24 22:23 ` Ansuel Smith
2023-04-27 7:34 ` Matthias Brugger
2023-04-25 7:27 ` Geert Uytterhoeven
2023-04-25 15:57 ` Rob Herring
2023-04-27 7:37 ` Matthias Brugger
2023-04-27 7:46 ` Geert Uytterhoeven
2023-04-27 7:48 ` Tony Lindgren
2023-05-02 8:15 ` Arnd Bergmann
2023-05-02 19:40 ` Rob Herring
2023-05-02 20:02 ` Krzysztof Kozlowski
2023-05-03 1:19 ` Shawn Guo
2023-05-03 10:43 ` Arnd Bergmann
2023-05-02 21:18 ` Linus Walleij
2023-05-02 21:27 ` Rob Herring
2023-05-02 22:01 ` Christian Hewitt
2023-05-03 10:42 ` Neil Armstrong
2023-05-02 22:52 ` Dmitry Baryshkov
2023-05-03 1:17 ` Rob Herring
2023-05-03 10:38 ` Arnd Bergmann
2023-05-03 12:13 ` Dmitry Baryshkov
2023-05-03 12:18 ` Arnd Bergmann
2023-05-03 13:16 ` Rob Herring
2023-05-03 20:37 ` Arnd Bergmann
2023-05-03 20:39 ` Linus Walleij
2023-05-03 22:22 ` Rob Herring
2023-05-02 23:02 ` Florian Fainelli
2023-05-03 1:04 ` Rob Herring [this message]
2023-05-03 22:29 ` Florian Fainelli
2023-05-03 5:57 ` Tony Lindgren
2023-05-03 8:56 ` Geert Uytterhoeven
2023-05-03 11:02 ` Arnd Bergmann
2023-05-03 13:08 ` Rob Herring
2023-05-03 20:25 ` Linus Walleij
2023-05-04 7:09 ` [Linux-stm32] " Alexandre TORGUE
2023-05-03 12:01 ` Jesper Nilsson
2023-05-04 10:11 ` Russell King (Oracle)
2023-05-04 11:44 ` Arnd Bergmann
2023-05-09 22:54 ` Jonathan Neuschäfer
2023-06-08 20:33 ` Rob Herring
2023-04-25 8:00 ` Krzysztof Kozlowski
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_JsqKRcMSijAdiP_BpyBGRuMhscZ12QFcLBAeZ+TcaQg7r4g@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=arnd@arndb.de \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=geert@linux-m68k.org \
--cc=kernel@dh-electronics.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-oxnas@groups.io \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-unisoc@lists.infradead.org \
--cc=olof@lixom.net \
--cc=openbmc@lists.ozlabs.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).