* Re: [RFC PATCH] gpio/omap: fix pm_runtime for IRQ functions [not found] ` <50FE61CB.5010906@ti.com> @ 2013-01-22 10:07 ` Linus Walleij 2013-01-27 13:05 ` Santosh Shilimkar 0 siblings, 1 reply; 2+ messages in thread From: Linus Walleij @ 2013-01-22 10:07 UTC (permalink / raw) To: Rajendra Nayak Cc: Santosh Shilimkar, Grant Likely, Jan Luebbe, Kevin Hilman, linux-omap, kernel, devicetree-discuss On Tue, Jan 22, 2013 at 10:54 AM, Rajendra Nayak <rnayak@ti.com> 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. Yours, Linus Walleij ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [RFC PATCH] gpio/omap: fix pm_runtime for IRQ functions 2013-01-22 10:07 ` [RFC PATCH] gpio/omap: fix pm_runtime for IRQ functions Linus Walleij @ 2013-01-27 13:05 ` Santosh Shilimkar 0 siblings, 0 replies; 2+ messages in thread From: Santosh Shilimkar @ 2013-01-27 13:05 UTC (permalink / raw) To: Linus Walleij Cc: Rajendra Nayak, Grant Likely, Jan Luebbe, Kevin Hilman, linux-omap, kernel, devicetree-discuss, Jon Hunter On Tuesday 22 January 2013 03:37 PM, Linus Walleij wrote: > On Tue, Jan 22, 2013 at 10:54 AM, Rajendra Nayak <rnayak@ti.com> 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-01-27 13:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1358531362-27933-1-git-send-email-jlu@pengutronix.de>
[not found] ` <50FCE27D.7060500@ti.com>
[not found] ` <CACRpkdYpCbWtk6PbgLm0HWFBihDqA_G_1btYQ38+WfeXridPJA@mail.gmail.com>
[not found] ` <50FE61CB.5010906@ti.com>
2013-01-22 10:07 ` [RFC PATCH] gpio/omap: fix pm_runtime for IRQ functions Linus Walleij
2013-01-27 13:05 ` Santosh Shilimkar
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).