On 12/12/2013 09:05 AM, Denis CIOCCA wrote:
why is mcspi1 your interrupt parent when you did a padconf for GPIO?
you want GPIO136, so you need the right gpio block as the interrupt
parent and map interrupts in the correct map.
see [1] for an example (omap2).
Oh my god! Now I've understand how device tree works...I'm sorry
Nishanth but the dt it's new for me...ok I'm using gpio5 and now it works!
+interrupt-parent = <&gpio5>;
+ interrupts = <8 IRQ_TYPE_LEVEL_HIGH>; /* gpio line 136 */
Thank you very much for your patience...;)
glad to hear it worked, yeah, device tree is a little different, but
logical in it's own way.
Regards,
Nishanth Menon
--
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
