From: David Miller <davem@davemloft.net>
To: grant.likely@secretlab.ca
Cc: thierry.reding@avionic-design.de, sparclinux@vger.kernel.org,
linus.walleij@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: SPARC and OF_GPIO
Date: Fri, 30 Nov 2012 11:46:51 -0500 (EST) [thread overview]
Message-ID: <20121130.114651.461648561907776096.davem@davemloft.net> (raw)
In-Reply-To: <20121130093520.631503E070C@localhost>
From: Grant Likely <grant.likely@secretlab.ca>
Date: Fri, 30 Nov 2012 09:35:20 +0000
> On non-sparc I've actually been moving in the direction of resolving
> resources at .probe time to make it easier to handle deferred probing.
> So if, for example, a device irq line is routed to a GPIO instead of the
> core interrupt controller, then the irq number won't be known until
> after the gpio driver .probe occurs. For addresses, this situation is
> unlikely, but for all the other kinds of resources (gpios, regs, clocks, irqs,
> etc) it is a problem that we're actually seeing.
Every interrupt in the device tree is resolvable with, at worst, very
small bus drivers, and that's what we pack into the generic sparc OF
device creation layer.
Actually much of it is generic and not bus type specific at all, and
is a simply mask and match into an interrupt routing table property.
next prev parent reply other threads:[~2012-11-30 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 9:53 Thierry Reding
2012-11-06 23:40 ` David Miller
2012-11-07 6:52 ` Thierry Reding
2012-11-07 7:34 ` David Miller
2012-11-30 9:35 ` Grant Likely
2012-11-30 9:40 ` Thierry Reding
2012-11-30 9:58 ` Grant Likely
2012-11-30 16:46 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-05 9:22 Thierry Reding
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=20121130.114651.461648561907776096.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=thierry.reding@avionic-design.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®