From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/9] ARM: Make a copy of the 2835 dts for the 2836.
Date: Thu, 23 Apr 2015 22:35:59 -0600 [thread overview]
Message-ID: <5539C82F.7000002@wwwdotorg.org> (raw)
In-Reply-To: <1429639796-2169-4-git-send-email-eric@anholt.net>
On 04/21/2015 12:09 PM, Eric Anholt wrote:
> This is not hooked up to anything yet, but it means that our later
> 2836-specific changes will be more obvious. The bcm2836-rpi-2-b.dts
> actually comes from bcm2835-rpi-2-b-plus, which apparently is the
> closest.
> arch/arm/boot/dts/bcm2836-rpi-2-b.dts | 30 +++++++++++++++++++++
> arch/arm/boot/dts/bcm2836-rpi.dtsi | 51 +++++++++++++++++++++++++++++++++++
> arch/arm/boot/dts/bcm2836.dtsi | 31 +++++++++++++++++++++
So we obviously need a new top-level bcm2836-rpi-2-b.dts for the new
board, and a new bcm2836.dtsi for the new SoC. However, do we really
need to duplicate bcm2836-rpi.dtsi? It should be identical between the
bcm2835/6 RPis, so I'd expect to just rename it to bcm283x-rpi.dtsi and
share it? The include of the SoC .dtsi file could be moved one level up
since that's the one difference?
Eventually, I'd like to get around to revamping the bcm283x DTs so
there's a DT for each separate board model, which would match the DT
filenames that U-Boot is looking for. Still, that's separate from these
patches.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Lee Jones <lee-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/9] ARM: Make a copy of the 2835 dts for the 2836.
Date: Thu, 23 Apr 2015 22:35:59 -0600 [thread overview]
Message-ID: <5539C82F.7000002@wwwdotorg.org> (raw)
In-Reply-To: <1429639796-2169-4-git-send-email-eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
On 04/21/2015 12:09 PM, Eric Anholt wrote:
> This is not hooked up to anything yet, but it means that our later
> 2836-specific changes will be more obvious. The bcm2836-rpi-2-b.dts
> actually comes from bcm2835-rpi-2-b-plus, which apparently is the
> closest.
> arch/arm/boot/dts/bcm2836-rpi-2-b.dts | 30 +++++++++++++++++++++
> arch/arm/boot/dts/bcm2836-rpi.dtsi | 51 +++++++++++++++++++++++++++++++++++
> arch/arm/boot/dts/bcm2836.dtsi | 31 +++++++++++++++++++++
So we obviously need a new top-level bcm2836-rpi-2-b.dts for the new
board, and a new bcm2836.dtsi for the new SoC. However, do we really
need to duplicate bcm2836-rpi.dtsi? It should be identical between the
bcm2835/6 RPis, so I'd expect to just rename it to bcm283x-rpi.dtsi and
share it? The include of the SoC .dtsi file could be moved one level up
since that's the one difference?
Eventually, I'd like to get around to revamping the bcm283x DTs so
there's a DT for each separate board model, which would match the DT
filenames that U-Boot is looking for. Still, that's separate from these
patches.
--
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
next prev parent reply other threads:[~2015-04-24 4:35 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 18:09 BCM2836 (Raspberry Pi 2) port Eric Anholt
2015-04-21 18:09 ` Eric Anholt
2015-04-21 18:09 ` [PATCH 1/9] dt-bindings: Add root properties for Raspberry Pi 2 Eric Anholt
2015-04-21 18:09 ` Eric Anholt
2015-04-24 4:27 ` Stephen Warren
2015-04-24 4:27 ` Stephen Warren
2015-04-21 18:09 ` [PATCH 2/9] ARM: BCM2835: Split peripheral definitions off to a common include Eric Anholt
2015-04-21 18:09 ` Eric Anholt
2015-04-24 4:28 ` Stephen Warren
2015-04-24 4:28 ` Stephen Warren
2015-04-21 18:09 ` [PATCH 3/9] ARM: Make a copy of the 2835 dts for the 2836 Eric Anholt
2015-04-21 18:09 ` Eric Anholt
2015-04-24 4:35 ` Stephen Warren [this message]
2015-04-24 4:35 ` Stephen Warren
2015-04-21 18:09 ` [PATCH 4/9] ARM: Update the device trees for 2836 Eric Anholt
2015-04-21 18:09 ` Eric Anholt
2015-04-24 4:36 ` Stephen Warren
2015-04-24 4:36 ` Stephen Warren
2015-04-21 18:09 ` [PATCH 5/9] ARM: BCM2836: Add io map initialization for bcm2836 Eric Anholt
2015-04-21 18:09 ` Eric Anholt
2015-04-21 18:53 ` Arnd Bergmann
2015-04-21 18:53 ` Arnd Bergmann
2015-04-21 20:37 ` Eric Anholt
2015-04-21 20:37 ` Eric Anholt
2015-04-21 21:11 ` Arnd Bergmann
2015-04-21 21:11 ` Arnd Bergmann
2015-04-21 23:02 ` Eric Anholt
2015-04-21 23:02 ` Eric Anholt
2015-04-22 7:22 ` Arnd Bergmann
2015-04-22 7:22 ` Arnd Bergmann
2015-04-24 7:16 ` Arnd Bergmann
2015-04-24 7:16 ` Arnd Bergmann
2015-04-21 18:09 ` [PATCH 6/9] ARM: Make a Kconfig option for shared BCM2835/BCM2836 code Eric Anholt
2015-04-21 18:09 ` Eric Anholt
2015-04-21 18:09 ` [PATCH 7/9] ARM: Add Kconfig support for bcm2836 Eric Anholt
2015-04-21 18:09 ` Eric Anholt
2015-04-21 18:59 ` Arnd Bergmann
2015-04-21 18:59 ` Arnd Bergmann
2015-04-21 20:38 ` Eric Anholt
2015-04-21 20:38 ` Eric Anholt
2015-04-24 3:30 ` Stephen Warren
2015-04-24 3:30 ` Stephen Warren
2015-04-21 18:09 ` [PATCH 8/9] ARM: Add MAINTAINERS for 2836 Eric Anholt
2015-04-21 18:09 ` Eric Anholt
2015-04-24 4:38 ` Stephen Warren
2015-04-24 4:38 ` Stephen Warren
2015-04-24 17:03 ` Eric Anholt
2015-04-24 17:03 ` Eric Anholt
2015-04-21 18:09 ` [PATCH 9/9] ARM: BCM283x: Register fixed clocks for uart in the DT Eric Anholt
2015-04-21 18:09 ` Eric Anholt
2015-04-24 4:44 ` Stephen Warren
2015-04-24 4:44 ` Stephen Warren
2015-04-24 17:06 ` Eric Anholt
2015-04-24 17:06 ` Eric Anholt
2015-04-25 4:23 ` Stephen Warren
2015-04-25 4:23 ` Stephen Warren
2015-04-24 4:25 ` BCM2836 (Raspberry Pi 2) port Stephen Warren
2015-04-24 4:25 ` Stephen Warren
2015-04-24 18:41 ` Eric Anholt
2015-04-24 18:41 ` Eric Anholt
2015-04-24 18:57 ` Stephen Warren
2015-04-24 18:57 ` Stephen Warren
2015-04-27 17:19 ` Eric Anholt
2015-04-27 17:19 ` Eric Anholt
2015-05-08 16:14 ` Alexander Stein
2015-05-08 16:14 ` Alexander Stein
2015-05-12 2:36 ` Stephen Warren
2015-05-12 2:36 ` Stephen Warren
2015-05-12 15:39 ` Alexander Stein
2015-05-12 15:39 ` Alexander Stein
2015-05-12 16:03 ` Stephen Warren
2015-05-12 16:03 ` Stephen Warren
2015-05-12 17:32 ` Eric Anholt
2015-05-12 17:32 ` Eric Anholt
2015-05-12 22:03 ` Stephen Warren
2015-05-12 22:03 ` Stephen Warren
2015-05-13 17:46 ` Eric Anholt
2015-05-13 17:46 ` Eric Anholt
2015-05-13 18:32 ` Stephen Warren
2015-05-13 18:32 ` Stephen Warren
2015-05-13 18:59 ` Eric Anholt
2015-05-13 18:59 ` Eric Anholt
2015-04-29 2:38 ` Stephen Warren
2015-04-29 2:38 ` Stephen Warren
2015-04-29 3:41 ` Florian Fainelli
2015-04-29 3:41 ` Florian Fainelli
2015-05-06 18:51 ` Eric Anholt
2015-05-06 18:51 ` Eric Anholt
2015-05-06 19:05 ` Arnd Bergmann
2015-05-06 19:05 ` Arnd Bergmann
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=5539C82F.7000002@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.