From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] DT irq deferred probe support
Date: Wed, 23 Apr 2014 16:43:26 -0700 [thread overview]
Message-ID: <20140423234326.GF6053@atomide.com> (raw)
In-Reply-To: <1398293861-7682-1-git-send-email-robherring2@gmail.com>
* Rob Herring <robherring2@gmail.com> [140423 15:58]:
> From: Rob Herring <robh@kernel.org>
>
> This is atleast the 4th attempt to fix a long standing issue with DT
> irq resolution needing to support deferred probe when irq parent is not
> yet initialized. This version implements Russell King's suggestion to do
> irq resolution when platform_get_irq is called.
>
> Tony, I squashed your warning fix (dropping the other part) and stole
> much of your commit message. Let me know if you have any issues with
> that.
Nope, looks good, just gave it a try and it fixes the problem for me.
Regards,
Tony
> Rob Herring (2):
> of: selftest: add deferred probe interrupt test
> of/irq: do irq resolution in platform_get_irq
>
> drivers/base/platform.c | 7 +++++-
> drivers/of/irq.c | 26 +++++++++++++++++++++
> drivers/of/platform.c | 4 +++-
> drivers/of/selftest.c | 32 ++++++++++++++++++++++++++
> drivers/of/testcase-data/tests-interrupts.dtsi | 12 ++++++++++
> include/linux/of_irq.h | 7 +++++-
> 6 files changed, 85 insertions(+), 3 deletions(-)
>
> --
> 1.9.1
>
prev parent reply other threads:[~2014-04-23 23:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 22:57 [PATCH 0/2] DT irq deferred probe support Rob Herring
2014-04-23 22:57 ` [PATCH 1/2] of: selftest: add deferred probe interrupt test Rob Herring
2014-04-23 22:57 ` [PATCH 2/2] of/irq: do irq resolution in platform_get_irq Rob Herring
2014-04-23 23:42 ` Tony Lindgren
2014-04-24 16:10 ` Grant Likely
2014-04-24 17:19 ` Tony Lindgren
2014-04-24 18:42 ` Thierry Reding
2014-04-24 20:47 ` Grant Likely
2014-04-23 23:43 ` Tony Lindgren [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=20140423234326.GF6053@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).