From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Rajendra Nayak <rnayak@ti.com>,
Grant Likely <grant.likely@secretlab.ca>,
Jan Luebbe <jlu@pengutronix.de>,
Kevin Hilman <khilman@deeprootsystems.com>,
linux-omap@vger.kernel.org, kernel@pengutronix.de,
devicetree-discuss@lists.ozlabs.org,
Jon Hunter <jon-hunter@ti.com>
Subject: Re: [RFC PATCH] gpio/omap: fix pm_runtime for IRQ functions
Date: Sun, 27 Jan 2013 18:35:24 +0530 [thread overview]
Message-ID: <51052614.5020606@ti.com> (raw)
In-Reply-To: <CACRpkdbtUo4oU_yjwukuYW89sk4OM0NY+ZcwQprLEu_9mqZFgg@mail.gmail.com>
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
prev parent reply other threads:[~2013-01-27 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 17:49 [RFC PATCH] gpio/omap: fix pm_runtime for IRQ functions Jan Luebbe
2013-01-21 6:38 ` Santosh Shilimkar
2013-01-22 8:22 ` Linus Walleij
2013-01-22 9:54 ` Rajendra Nayak
2013-01-22 10:07 ` Linus Walleij
2013-01-27 13:05 ` Santosh Shilimkar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51052614.5020606@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jlu@pengutronix.de \
--cc=jon-hunter@ti.com \
--cc=kernel@pengutronix.de \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.