From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: convert ARM RealView to common clk
Date: Wed, 08 Aug 2012 14:06:10 +0100 [thread overview]
Message-ID: <1344431170.2435.47.camel@hornet> (raw)
In-Reply-To: <CACRpkdYkoeH09H6c4WEw40hpP9+oRD4pa0-yBk1L02yfao2sgg@mail.gmail.com>
On Wed, 2012-08-08 at 12:55 +0100, Linus Walleij wrote:
> On Wed, Aug 8, 2012 at 1:52 PM, Pawel Moll <pawel.moll@arm.com> wrote:
>
> >> ------------[ cut here ]------------
> >> WARNING: at /home/pawmol01/src/kernel.org/linux/kernel/timer.c:1076 del_timer_sync+0x34/0x5c()
> >
> > Err. Ignore that. The same happens without your patch :-)
> >
> > Will try with 3.5.
>
> Hm it boots like a charm on PB1176, what's so very different about the EB?
It's configuration difference, I guess. You may try enabling
CONFIG_LEDS_TRIGGERS (not that it makes much sense on Realview) if you
want to see the same effect :-)
It seems that a0193cbee0809d65362a0767b2d50306b145b2f5 "leds: use
led_set_brightness in led_trigger_event" causes a problem when
led_trigger_event() is called from an interrupt context. I'll let the
LEDS people know.
> Oh well. Are you maintaining RealView EB, BTW?
Not really. At least I didn't have any reason to do this so far. And the
only Realview platforms I'm really interested in are the EB models. DT
for Realview is on my todo list, but with really low priority (around
"most likely will never happen").
Anyway, after testing your change on EB model:
Acked-by: Pawel Moll <pawel.moll@arm.com>
Cheers!
Pawe?
next prev parent reply other threads:[~2012-08-08 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 16:32 [PATCH] clk: convert ARM RealView to common clk Linus Walleij
2012-08-08 11:48 ` Pawel Moll
2012-08-08 11:52 ` Pawel Moll
2012-08-08 11:55 ` Linus Walleij
2012-08-08 13:06 ` Pawel Moll [this message]
2012-08-16 12:56 ` Linus Walleij
2012-08-22 12:09 ` Linus Walleij
2012-08-24 23:51 ` Mike Turquette
2012-08-30 12:33 ` Pawel Moll
2012-08-30 17:24 ` Linus Walleij
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=1344431170.2435.47.camel@hornet \
--to=pawel.moll@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).