From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: dts: Add minimal support for dm8168-evm
Date: Tue, 17 Mar 2015 17:06:52 -0700 [thread overview]
Message-ID: <20150318000652.GJ31346@atomide.com> (raw)
In-Reply-To: <20150202160932.GF16250@atomide.com>
* Tony Lindgren <tony@atomide.com> [150202 08:15]:
> * Matthijs van Duin <matthijsvanduin@gmail.com> [150131 17:54]:
> > I just noticed the dm816x.dtsi says:
> >
> > ocp {
> > compatible = "ti,omap3-l3-smx", "simple-bus";
> >
> > This is incorrect: the DM81xx (and siblings like the AM335x) use
> > Arteris FlexNOC for the L3 interconnect, same as omap4/5 and vayu, not
> > SonicsMX. (In general everything on the DM81xx seems to be
> > omap4-generation)
>
> Good catch, yes it seems it's mostly omap4. Looks like we
> should also add it for am33xx.dtsi while at it.
>
> I'll also check the devices one more time if I have some as
> compatible with omap3 instead of omap4.
Hmm this is also broken on am33xx, and the following patch is needed.
And we also need to populate the tables along the lines of 27b7d5f3cc49
("bus: omap_l3_noc: Add AM4372 interconnect error data").
Do the below ranges match your JTAG results? I scanned them in u-boot
using md for the ranges where I found some related data.
That got me wondering if we can actually scan that data based
on the ranges below as target is 00130001 and flagmux 00370001.
We would be missing the names, but that would be still less data
to pile up in the kernel :) If some module is disabled, then it
should never produce errors so it seems safe to scan the data..
Can we dig even more info based on the RX port address at offset
0x10? That's the L3_TARG_STDHOSTHDR_NTTPADDR_0.
Or got any good ideas for populating the names?
Regards,
Tony
8< ------------------------------
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi
@@ -105,7 +105,10 @@
* the whole bus hierarchy.
*/
ocp {
- compatible = "simple-bus";
+ compatible = "ti,am335-l3-noc", "simple-bus";
+ reg = <0x44000000 0x1200
+ 0x44800000 0x1000>;
+ interrupts = <9 10>;
#address-cells = <1>;
#size-cells = <1>;
ranges;
--- a/arch/arm/boot/dts/dm816x.dtsi
+++ b/arch/arm/boot/dts/dm816x.dtsi
@@ -58,8 +58,10 @@
* the whole bus hierarchy.
*/
ocp {
- compatible = "ti,omap4-l3-noc", "simple-bus";
- reg = <0x44000000 0x10000>;
+ compatible = "ti,dm816-l3-noc", "simple-bus";
+ reg = <0x44000000 0x1200
+ 0x44400000 0x1200
+ 0x44800000 0x1000>;
interrupts = <9 10>;
#address-cells = <1>;
#size-cells = <1>;
next prev parent reply other threads:[~2015-03-18 0:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 23:37 [PATCH 0/4] Device tree related changes to boot dm816x Tony Lindgren
2015-01-13 23:37 ` [PATCH 1/4] ARM: OMAP2+: Add board-generic.c entry for ti81xx Tony Lindgren
2015-01-14 13:51 ` Sergei Shtylyov
2015-01-15 0:07 ` Tony Lindgren
2015-01-19 19:18 ` Tony Lindgren
2015-01-19 20:42 ` Felipe Balbi
2015-01-19 21:05 ` Tony Lindgren
2015-01-19 21:10 ` Felipe Balbi
2015-01-13 23:37 ` [PATCH 2/4] ARM: dts: Add basic dm816x device tree configuration Tony Lindgren
2015-01-15 21:23 ` Suman Anna
2015-01-15 22:59 ` Tony Lindgren
2015-01-17 16:41 ` Tony Lindgren
2015-01-13 23:37 ` [PATCH 3/4] ARM: dts: Add basic clocks for dm816x Tony Lindgren
2015-01-13 23:37 ` [PATCH 4/4] ARM: dts: Add minimal support for dm8168-evm Tony Lindgren
2015-01-17 16:47 ` Tony Lindgren
2015-01-17 17:51 ` Matthijs van Duin
2015-01-17 18:14 ` Tony Lindgren
2015-01-17 22:37 ` Matthijs van Duin
2015-01-19 17:29 ` Tony Lindgren
2015-01-22 3:17 ` Matthijs van Duin
2015-01-23 16:47 ` Tony Lindgren
2015-01-25 8:34 ` Matthijs van Duin
2015-01-26 15:58 ` Tony Lindgren
2015-01-28 21:43 ` Matthijs van Duin
2015-02-02 17:44 ` Tony Lindgren
2015-02-03 5:51 ` Matthijs van Duin
2015-01-28 17:04 ` Tony Lindgren
2015-02-01 1:51 ` Matthijs van Duin
2015-02-02 16:09 ` Tony Lindgren
2015-03-18 0:06 ` Tony Lindgren [this message]
2015-03-18 8:32 ` Matthijs van Duin
2015-03-18 16:54 ` Tony Lindgren
2015-03-19 5:13 ` Matthijs van Duin
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=20150318000652.GJ31346@atomide.com \
--to=tony@atomide.com \
--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).