linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rmallon@gmail.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: ep93xx irq-vic regression
Date: Sat, 16 Mar 2013 10:11:48 +1100	[thread overview]
Message-ID: <5143AAB4.6020406@gmail.com> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F0020980106C9F@AUSP01VMBX24.collaborationhost.net>

On 16/03/13 08:46, H Hartley Sweeten wrote:

>  Hello all,
> 
> Yesterday I tried upgrading my ep93xx system from 3.6.6 to 3.8.3.
> The kernel compiles fine but the machine would not boot. It just
> hangs when the bootloader (RedBoot) tries to exec the kernel.
> 
> I then tried 3.7.0 and it works fine.
> 
> I did a bisect and got down to this commit:
> 
> $ git bisect bad
> 07c9249f1fa90cc8189bed44c0bcece664596a72 is the first bad commit
> commit 07c9249f1fa90cc8189bed44c0bcece664596a72
> Author: Linus Walleij <linus.walleij@linaro.org>
> Date:   Tue Oct 16 18:50:00 2012 +0100
> 
>     ARM: 7554/1: VIC: use irq_domain_add_simple()
> 
> Any ideas on what might be the problem?


I don't know the code very well, but looking at the change we go
from being having the first vic bank being registered with
irq_domain_add_legacy to irq_domain_add_linear (since first_irq
is zero). It looks like the linear domain needs to have it's
revmap initialised with a call to either irq_domain_associate_many
or irq_create_strict_mappings, which I can't find a call to. Are
we left with the first vic bank having no revmap? That's from a
ten minute, uninformed glance at the code though, so I might be
off base :-).

~Ryan

  reply	other threads:[~2013-03-15 23:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 21:46 ep93xx irq-vic regression H Hartley Sweeten
2013-03-15 23:11 ` Ryan Mallon [this message]
2013-03-16  0:16   ` H Hartley Sweeten
2013-03-16 13:49     ` Florian Fainelli
2013-03-17  0:06       ` Ryan Mallon
2013-03-17 14:48         ` Florian Fainelli
2013-03-18 20:21     ` Linus Walleij
2013-03-19 17:03       ` H Hartley Sweeten

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=5143AAB4.6020406@gmail.com \
    --to=rmallon@gmail.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).