From: broonie@opensource•wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists•infradead.org
Subject: Boot breaks in -next from LEGACY to LINEAR conversion
Date: Wed, 18 Jul 2012 17:10:23 +0100 [thread overview]
Message-ID: <20120718161023.GE4495@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120717185749.GJ4477@opensource.wolfsonmicro.com>
On Tue, Jul 17, 2012 at 07:57:49PM +0100, Mark Brown wrote:
> -next fails to boot for me today on my s3c64xx based systems. Walking
> back to the last time I tried and bisecting likely branches I find that
> commit 910139 (irqdomain: Replace LEGACY mapping with LINEAR) is the one
> that introduces the build break. Unfortunately the boot fails before I
> get a console which makes diagnosis somewhat more tricky than would be
> ideal. Any ideas?
Further data: the irq_domain_associate_many() calls that we're now doing
are also causing WARN_ON()s to go off during boot after commit 98aa46
(irqdomain: Support for static IRQ mapping and association) causing
breakage for my interrupt using MFDs.
I don't really have time to investigate now but backing out that commit
seems to make things much happier, I suspect there's some collision with
IRQs allocated statically by the platform but I don't immediately see
what's new here.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120718/a55fdf50/attachment.sig>
next prev parent reply other threads:[~2012-07-18 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 18:57 Boot breaks in -next from LEGACY to LINEAR conversion Mark Brown
2012-07-18 0:52 ` Paul Mundt
2012-07-18 10:16 ` Mark Brown
2012-07-18 16:10 ` Mark Brown [this message]
2012-07-18 16:27 ` Grant Likely
2012-07-20 4:30 ` Grant Likely
2012-07-20 9:42 ` Mark Brown
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=20120718161023.GE4495@opensource.wolfsonmicro.com \
--to=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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