Skip to contentSkip to conversation

ARM: dts: omap3-igep: fix boot fail due wrong compatible match

PATCH New Javier Martinez Canillas 3 participants 5 messages Feb 22, 2014 – Feb 28, 2014 Device tree bindings

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ARM: dts: omap3-igep: fix boot fail due wrong compatible match

This patch is based on commit:

016c12d2 ("ARM: OMAP3: Fix hardware detection for omap3630 when booted with device tree")

and fixes a boot hang due the IGEP board being wrongly initialized as an OMAP3430 platform instead of an OMAP3630.

---

Tony and Benoit,

Sorry for posting this patch this late on the -rc cycle but I just didn't have time before to test IGEP boards against 3.14.

I hope this fix can still make it to 3.14 since is a very big issue (board not even booting).

Thanks a lot and best regards,
Javier

 arch/arm/boot/dts/omap3-igep0020.dts | 2 +-
 arch/arm/boot/dts/omap3-igep0030.dts | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
arch/arm/boot/dts/omap3-igep0020.dts +1 -1
index 25a2b5f..f2779ac 100644
@@ -14,7 +14,7 @@
 
 / {
 	model = "IGEPv2 (TI OMAP AM/DM37x)";
-	compatible = "isee,omap3-igep0020", "ti,omap3";
+	compatible = "isee,omap3-igep0020", "ti,omap36xx", "ti,omap3";
 
 	leds {
 		pinctrl-names = "default";
arch/arm/boot/dts/omap3-igep0030.dts +1 -1
index 145c58c..2793749 100644
@@ -13,7 +13,7 @@
 
 / {
 	model = "IGEP COM MODULE (TI OMAP AM/DM37x)";
-	compatible = "isee,omap3-igep0030", "ti,omap3";
+	compatible = "isee,omap3-igep0030", "ti,omap36xx", "ti,omap3";
 
 	leds {
 		pinctrl-names = "default";
Signature · 1 line
1.8.5.3
#1 lore raw

PATCH 1/1 ARM: dts: omap3-igep: fix boot fail due wrong compatible match

Hi Tony,

Quoted 52 lines · Javier Martinez Canillas

This patch is based on commit:

016c12d2 ("ARM: OMAP3: Fix hardware detection for omap3630 when booted with device tree")

and fixes a boot hang due the IGEP board being wrongly initialized as an OMAP3430 platform instead of an OMAP3630.

---

Tony and Benoit,

Sorry for posting this patch this late on the -rc cycle but I just didn't have time before to test IGEP boards against 3.14.

I hope this fix can still make it to 3.14 since is a very big issue (board not even booting).

Thanks a lot and best regards,
Javier

 arch/arm/boot/dts/omap3-igep0020.dts | 2 +-
 arch/arm/boot/dts/omap3-igep0030.dts | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
arch/arm/boot/dts/omap3-igep0020.dts +1 -1
index 25a2b5f..f2779ac 100644
@@ -14,7 +14,7 @@
 
 / {
        model = "IGEPv2 (TI OMAP AM/DM37x)";
-       compatible = "isee,omap3-igep0020", "ti,omap3";
+       compatible = "isee,omap3-igep0020", "ti,omap36xx", "ti,omap3";
 
        leds {
                pinctrl-names = "default";
arch/arm/boot/dts/omap3-igep0030.dts +1 -2
index 145c58c..2793749 100644
@@ -13,7 +13,7 @@
 
 / {
        model = "IGEP COM MODULE (TI OMAP AM/DM37x)";
-       compatible = "isee,omap3-igep0030", "ti,omap3";
+       compatible = "isee,omap3-igep0030", "ti,omap36xx", "ti,omap3";
 
        leds {
                pinctrl-names = "default";
--
Quoted 2 lines

1.8.5.3

I saw you send a pull request for 3.14-rc4 fixes and this fix was not included.

Are you planning to send more fixes for 3.14?

Thanks a lot and best regards,
Javier

#2 lore raw

PATCH 1/1 ARM: dts: omap3-igep: fix boot fail due wrong compatible match

Quoted 61 lines · Javier Martinez Canillas

Hi Tony,

Quoted 52 lines · Javier Martinez Canillas

This patch is based on commit:

016c12d2 ("ARM: OMAP3: Fix hardware detection for omap3630 when booted with device tree")

and fixes a boot hang due the IGEP board being wrongly initialized as an OMAP3430 platform instead of an OMAP3630.

---

Tony and Benoit,

Sorry for posting this patch this late on the -rc cycle but I just didn't have time before to test IGEP boards against 3.14.

I hope this fix can still make it to 3.14 since is a very big issue (board not even booting).

Thanks a lot and best regards,
Javier

 arch/arm/boot/dts/omap3-igep0020.dts | 2 +-
 arch/arm/boot/dts/omap3-igep0030.dts | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
arch/arm/boot/dts/omap3-igep0020.dts +1 -1
index 25a2b5f..f2779ac 100644
@@ -14,7 +14,7 @@
 
 / {
        model = "IGEPv2 (TI OMAP AM/DM37x)";
-       compatible = "isee,omap3-igep0020", "ti,omap3";
+       compatible = "isee,omap3-igep0020", "ti,omap36xx", "ti,omap3";
 
        leds {
                pinctrl-names = "default";
arch/arm/boot/dts/omap3-igep0030.dts +1 -2
index 145c58c..2793749 100644
@@ -13,7 +13,7 @@
 
 / {
        model = "IGEP COM MODULE (TI OMAP AM/DM37x)";
-       compatible = "isee,omap3-igep0030", "ti,omap3";
+       compatible = "isee,omap3-igep0030", "ti,omap36xx", "ti,omap3";
 
        leds {
                pinctrl-names = "default";
--
Quoted 2 lines

1.8.5.3

I saw you send a pull request for 3.14-rc4 fixes and this fix was not included.

Quoted 1 line

Are you planning to send more fixes for 3.14?

Yes hoping to send one more set, got this one tagged for it.

Regards,

Tony

#3 lore raw

PATCH 1/1 ARM: dts: omap3-igep: fix boot fail due wrong compatible match

Hi Tony,

Quoted 62 lines · Tony Lindgren
Quoted 61 lines · Javier Martinez Canillas

Hi Tony,

Quoted 52 lines · Javier Martinez Canillas

This patch is based on commit:

016c12d2 ("ARM: OMAP3: Fix hardware detection for omap3630 when booted with device tree")

and fixes a boot hang due the IGEP board being wrongly initialized as an OMAP3430 platform instead of an OMAP3630.

---

Tony and Benoit,

Sorry for posting this patch this late on the -rc cycle but I just didn't have time before to test IGEP boards against 3.14.

I hope this fix can still make it to 3.14 since is a very big issue (board not even booting).

Thanks a lot and best regards,
Javier

 arch/arm/boot/dts/omap3-igep0020.dts | 2 +-
 arch/arm/boot/dts/omap3-igep0030.dts | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
arch/arm/boot/dts/omap3-igep0020.dts +1 -1
index 25a2b5f..f2779ac 100644
@@ -14,7 +14,7 @@
 
 / {
        model = "IGEPv2 (TI OMAP AM/DM37x)";
-       compatible = "isee,omap3-igep0020", "ti,omap3";
+       compatible = "isee,omap3-igep0020", "ti,omap36xx", "ti,omap3";
 
        leds {
                pinctrl-names = "default";
arch/arm/boot/dts/omap3-igep0030.dts +1 -2
index 145c58c..2793749 100644
@@ -13,7 +13,7 @@
 
 / {
        model = "IGEP COM MODULE (TI OMAP AM/DM37x)";
-       compatible = "isee,omap3-igep0030", "ti,omap3";
+       compatible = "isee,omap3-igep0030", "ti,omap36xx", "ti,omap3";
 
        leds {
                pinctrl-names = "default";
--
Quoted 2 lines

1.8.5.3

I saw you send a pull request for 3.14-rc4 fixes and this fix was not included.

Quoted 4 lines
Quoted 1 line

Are you planning to send more fixes for 3.14?

Yes hoping to send one more set, got this one tagged for it.

Great, thanks a lot for your help!

Best regards,
Javier

#4 lore raw

PATCH 1/1 ARM: dts: omap3-igep: fix boot fail due wrong compatible match

Quoted 11 lines · Javier Martinez Canillas
Quoted 8 lines · Tony Lindgren
Quoted 4 lines · Javier Martinez Canillas

I saw you send a pull request for 3.14-rc4 fixes and this fix was not included.

Are you planning to send more fixes for 3.14?

Yes hoping to send one more set, got this one tagged for it.

Great, thanks a lot for your help!

Applied to omap-for-v3.14/fixes and pushed out now thanks.

Tony