From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: vexpress issues in next-20121029
Date: Mon, 29 Oct 2012 14:24:48 -0600 [thread overview]
Message-ID: <508EE610.9050703@wwwdotorg.org> (raw)
Pawel,
I see two issues on vexpress in next-20121029:
1) At compile-time: v2m_timer_init() and v2m_dt_timer_init() reference
functions vexpress_clk_init() and vexpress_clk_of_init() respectively,
which don't appear anywhere in the source tree.
2) With those calls commented out, I find that
vexpress_sysreg_init_leds() is device_initcall, and so executes even
when not running on vexpress HW. This crashes on Tegra (which I have
converted to single-zImage locally).
These appear to come from the following commits:
0891642 ARM: vexpress: Start using new Versatile Express infrastructure
568e5e4 mfd: Versatile Express system registers driver
next reply other threads:[~2012-10-29 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 20:24 Stephen Warren [this message]
2012-10-30 16:16 ` vexpress issues in next-20121029 Pawel Moll
2012-11-05 9:35 ` Russell King - ARM Linux
2012-11-05 9:45 ` Russell King - ARM Linux
2012-11-05 14:43 ` Pawel Moll
2012-11-05 16:47 ` Arnd Bergmann
2012-11-05 17:19 ` Pawel Moll
2012-11-05 17:52 ` Arnd Bergmann
2012-11-05 18:12 ` Pawel Moll
2012-11-07 20:36 ` Stephen Warren
2012-11-08 18:54 ` Pawel Moll
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=508EE610.9050703@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--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