On Tuesday 22 January 2013 03:37 PM, Linus Walleij wrote:
On Tue, Jan 22, 2013 at 10:54 AM, Rajendra Nayak <rnayak@xxxxxx> wrote:
On Tuesday 22 January 2013 01:52 PM, Linus Walleij wrote:
In the Nomadik I had a similar situation with a GPIO used for the
ethernet IRQ. I put the GPIO number in a special board-specific
node and added this to the machine,
Thanks Linus. Are there any bindings already available on how these
special board-specific nodes can be defined in the dts files?
No generic bindings as they are per definition board-specific.
So in the Nomadik case it looks like this:
/* Custom board node with GPIO pins to active etc */
usb-s8815 {
/* The S8815 is using this very GPIO pin for the SMSC91x IRQs */
ethernet-gpio {
gpios = <&gpio3 19 0x1>;
interrupts = <19 0x1>;
interrupt-parent = <&gpio3>;
};
/* This will bias the MMC/SD card detect line */
mmcsd-gpio {
gpios = <&gpio3 16 0x1>;
};
};
First I added custom nodes to the IP blocks, but it was no good idea
as it's not generic for that driver at all, just a board pecularity.
Are there any using some such in the mainline already?
I just sent a pull request for the Nomadik example but I don't
know about any others.
Thanks Linus for the pointer.
Regards
Santosh
--
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
