From: Marc Zyngier <marc.zyngier@arm.com>
To: linux-sh@vger.kernel.org
Subject: Re: ARM: shmobile: r8a73a4: Instantiate GIC from C board code in legacy builds
Date: Wed, 21 Jan 2015 11:04:10 +0000 [thread overview]
Message-ID: <54BF87AA.5050507@arm.com> (raw)
In-Reply-To: <20150120113800.11062.65299.sendpatchset@little-apple>
On 21/01/15 10:38, Geert Uytterhoeven wrote:
> On Wed, Jan 21, 2015 at 11:15 AM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>>> arch_timer: No interrupt available, giving up
>>> sched_clock: 32 bits at 128 Hz, resolution 7812500ns, wraps every 16777216000000000ns
>>> Console: colour dummy device 80x30
>>> Calibrating delay loop...
>>
>> That's because you seems to be using a horrible mix of DT devices (arch
>> timers, for example), and hardcoded devices, with the added complexity
>> of having secondary interrupt controllers.
>>
>> The only workaround I can think of is to patch the hardcoded interrupts
>> at boot time with something similar to what I cooked there:
>>
>> http://www.spinics.net/lists/linux-omap/msg114814.html
>>
>> At the moment, you either end-up with no interrupts for the DT devices
>> (as above), or with an exploding system because the hardcoded interrupts
>> completely wrong (as in the original post).
>>
>> I don't have access to such hardware, but I'm happy to help.
>
> Thanks!
>
> That solution looks convoluted to me, especially since we do have patches
> available to convert r8a73a4 to multiplatform-only.
If you don't mind having a cycle with a broken board, my vote is to go
for full multiplatform. It makes my job much easier! ;-)
> That won't make it in v3.19 this late in the cycle, but if we push hard, v3.20
> should be doable IMHO.
OK. In any case, let me know if I can help you with this transition.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-01-21 11:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 11:38 ARM: shmobile: r8a73a4: Instantiate GIC from C board code in legacy builds Magnus Damm
2015-01-20 23:50 ` Simon Horman
2015-01-21 1:59 ` Simon Horman
2015-01-21 8:57 ` Geert Uytterhoeven
2015-01-21 9:25 ` Simon Horman
2015-01-21 10:08 ` Geert Uytterhoeven
2015-01-21 10:15 ` Marc Zyngier
2015-01-21 10:38 ` Geert Uytterhoeven
2015-01-21 11:04 ` Marc Zyngier [this message]
2015-01-21 12:50 ` Geert Uytterhoeven
2015-01-22 2:23 ` Simon Horman
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=54BF87AA.5050507@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.