linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: punit.agrawal@arm.com (Punit Agrawal)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers: CCI: add ARM CCI PMU support
Date: Mon, 12 Aug 2013 17:58:28 +0100	[thread overview]
Message-ID: <52091434.3020700@arm.com> (raw)
In-Reply-To: <20130812160835.GE25995@mudshark.cambridge.arm.com>

Hi Will,

On 12/08/13 17:08, Will Deacon wrote:
> [replying to self]
>
> On Mon, Aug 12, 2013 at 02:59:03PM +0100, Will Deacon wrote:
>> So, I just tried to test this patch but I'm getting issues when enabling CCI
>> with mainline:
>>
>>
>> ARM Versatile Express Boot Monitor
>> Version:    V5.1.5
>> Build Date: Jul 24 2012
>> Daughterboard Site 1: V2P-CA15 Cortex A15
>> Daughterboard Site 2: V2P-CA15_A7 Cortex A15
>> Running boot script from flash - BOOTSCRIPT
>> Loaded kernel - linuxtc2
>> Booting kernel @ 0x80008000
>> Command line 'ip=dhcp root=/dev/nfs nfsroot=10.1.203.36:/exports/linaro-13.06,tcp rw console=ttyAMA0,38400 mem=2G loglevel=9 user_debug=31 earlyprintk debug'
>> ATAGs @ 0x80000100
>>
>>
>> Fatal Error: Unhandled Exception - Undefined
>>
>>
>> We're exploding *really* early, and I have no idea why. If I remove CCI from
>> the equation (either in the kernel or the device-tree), then I can boot as
>> per usual.
>
> Turns out my .dtb has gone over some limit and appended dtb corrupts the
> kernel image. Removing some random nodes got things working again.
>

Just saw your mail. I haven't run into this one before. But looks like 
you've figured out what the problem was.

Let me know if you hit any issues with testing / using the CCI PMU.

Thanks for picking this up.

Punit

> Will
>
>

  reply	other threads:[~2013-08-12 16:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11  3:00 [PATCH] drivers: CCI: add ARM CCI PMU support Punit Agrawal
2013-08-05 11:37 ` Punit Agrawal
2013-08-07  1:45   ` Will Deacon
2013-08-12 13:59     ` Will Deacon
2013-08-12 16:08       ` Will Deacon
2013-08-12 16:58         ` Punit Agrawal [this message]
2013-08-14 21:03 ` Kumar Gala
2013-08-14 22:38   ` Rob Herring
2013-08-15 10:01     ` Punit Agrawal
2013-08-15  9:10   ` Punit Agrawal
2013-08-15 16:25     ` Kumar Gala
2013-08-16 10:31       ` Punit Agrawal
2013-08-16 10:53         ` Kumar Gala
2013-08-15 19:00     ` Kumar Gala
2013-08-16 10:56       ` Punit Agrawal
2013-08-16 11:31         ` Kumar Gala
2013-08-16 12:41           ` Punit Agrawal
2013-08-14 21:06 ` Stephen Warren
2013-08-14 21:09   ` Kumar Gala
2013-08-14 21:13     ` Stephen Warren
2013-08-14 21:16       ` Kumar Gala
2013-08-15 10:09         ` Punit Agrawal
2013-08-16 17:19 ` [PATCH v2] " Punit Agrawal
2013-08-16 18:31   ` Stephen Warren
2013-08-19 11:14     ` Punit Agrawal
2013-08-19 16:15       ` Stephen Warren
2013-08-16 18:47   ` Kumar Gala
2013-08-19 11:21     ` Punit Agrawal
2013-08-20 15:07   ` Will Deacon

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=52091434.3020700@arm.com \
    --to=punit.agrawal@arm.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).