devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Linton <lintonrjeremy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org
Subject: pSeries boot failure due to wrong interrupt controller
Date: Mon, 22 Jun 2015 14:44:18 -0500	[thread overview]
Message-ID: <CAEFTgiyHkf8ooYdWW0nTLcdraJ_L9FpLSVZa4KS3CcdpGWJxew@mail.gmail.com> (raw)

The OF IRQ logic was refactored a while back, and it appears that it
broke the case where a device doesn't have an interrupt-map
(legacy/ISA platform peripherals). In particular on the older pSeries
platforms the console serial port (keyboard/etc) is attached via a
Winbond super I/O controller. With the refactored logic
of_irq_parse_raw() returns with the out_irq->np pointing at the bus,
rather than the interrupt controller. This results in the platform
logic getting confused about the appropriate interrupt host, and in
ics_rtas_host_match() it doesn't match "chrp,iic" and the xics takes
over and tries to use RTAS to map the interrupt. RTAS then crashes the
machine.

This tweaks the "-> no map, getting parent" behavior to behave as
before, and the machine boots.

Thanks

Signed-off-by: Jeremy Linton <lintonrjeremy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


diff --git a/drivers/of/irq.c b/drivers/of/irq.c
index 1a79806..78b4161b 100644
--- a/drivers/of/irq.c
+++ b/drivers/of/irq.c
@@ -252,7 +252,6 @@ int of_irq_parse_raw(const __be32 *addr, struct
of_phandle_args *out_irq)
                 * Successfully parsed an interrrupt-map translation; copy new
                 * interrupt specifier into the out_irq structure
                 */
-               out_irq->np = newpar;

                match_array = imap - newaddrsize - newintsize;
                for (i = 0; i < newintsize; i++)
@@ -262,6 +261,7 @@ int of_irq_parse_raw(const __be32 *addr, struct
of_phandle_args *out_irq)

        skiplevel:
                /* Iterate again with new parent */
+               out_irq->np=newpar;
                pr_debug(" -> new parent: %s\n", of_node_full_name(newpar));
                of_node_put(ipar);
                ipar = newpar;
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in

             reply	other threads:[~2015-06-22 19:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 19:44 Jeremy Linton [this message]
     [not found] ` <CAEFTgiyHkf8ooYdWW0nTLcdraJ_L9FpLSVZa4KS3CcdpGWJxew-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-23 13:42   ` pSeries boot failure due to wrong interrupt controller Rob Herring
     [not found]     ` <CAL_JsqJqkUL8XyqR6yjg+-thj4YOQ6cUohGHHid71tdRFft7vw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-26 17:54       ` Jeremy Linton
     [not found]         ` <558D91C1.6030004-WMdfZNuR64nqlBn2x/YWAg@public.gmane.org>
2015-06-26 21:54           ` Benjamin Herrenschmidt
     [not found]             ` <1435355687.26815.8.camel-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2015-06-26 22:35               ` Jeremy Linton
     [not found]                 ` <558DD3C8.6000800-WMdfZNuR64nqlBn2x/YWAg@public.gmane.org>
2015-06-26 22:38                   ` Benjamin Herrenschmidt

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=CAEFTgiyHkf8ooYdWW0nTLcdraJ_L9FpLSVZa4KS3CcdpGWJxew@mail.gmail.com \
    --to=lintonrjeremy-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.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).