* Tony Lindgren <tony@xxxxxxxxxxx> [150529 10:28]:
> The interconnects on dm816x are like on omap4, so we should use
> l3-noc instead of l3-smx. But as the related SoC specific
> l3_target_data is still missing from omap_l3_noc let's just
> remove the entry for now.
>
> Cc: Brian Hutchinson <b.hutchman@xxxxxxxxx>
> Reported-by: Matthijs van Duin <matthijsvanduin@xxxxxxxxx>
> Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx>
> ---
> arch/arm/boot/dts/dm816x.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/dm816x.dtsi b/arch/arm/boot/dts/dm816x.dtsi
> index 289806a..3c99cfa 100644
> --- a/arch/arm/boot/dts/dm816x.dtsi
> +++ b/arch/arm/boot/dts/dm816x.dtsi
> @@ -58,7 +58,7 @@
> * the whole bus hierarchy.
> */
> ocp {
> - compatible = "ti,omap3-l3-smx", "simple-bus";
> + compatible = "simple-bus";
> reg = <0x44000000 0x10000>;
> interrupts = <9 10>;
> #address-cells = <1>;
We should remove reg and interrupts too, updated patch below.
Regards,
Tony
8< ---------------
From: Tony Lindgren <tony@xxxxxxxxxxx>
Date: Mon, 16 Mar 2015 18:04:20 -0700
Subject: [PATCH] ARM: dts: Remove L3 compatible value for dm816x
The interconnects on dm816x are like on omap4, so we should use
l3-noc instead of l3-smx. But as the related SoC specific
l3_target_data is still missing from omap_l3_noc let's just
remove the entry for now. And as we're updating the dts files
to follow the interconnect layout, this module will not be at
the top level.
Cc: Brian Hutchinson <b.hutchman@xxxxxxxxx>
Reported-by: Matthijs van Duin <matthijsvanduin@xxxxxxxxx>
Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx>
--- a/arch/arm/boot/dts/dm816x.dtsi
+++ b/arch/arm/boot/dts/dm816x.dtsi
@@ -58,9 +58,7 @@
* the whole bus hierarchy.
*/
ocp {
- compatible = "ti,omap3-l3-smx", "simple-bus";
- reg = <0x44000000 0x10000>;
- interrupts = <9 10>;
+ compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <1>;
ranges;
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
