From: Daniel Tang <dt.tangr@gmail.com>
To: Fabian Vogt <fabian@ritter-vogt.de>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org, linux@arm.linux.org.uk,
"Lionel Debroux" <lionel_debroux@yahoo.fr>,
linux-kernel@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: [RFC PATCH arm: initial TI-Nspire support]
Date: Tue, 9 Apr 2013 15:59:52 +1000 [thread overview]
Message-ID: <29D8E742-C870-45AE-B102-13A477AE6419@gmail.com> (raw)
In-Reply-To: <op.wu8k5pwqu7prd4@fabians-laptop.fritz.box>
On 09/04/2013, at 5:16 AM, Fabian Vogt <fabian@ritter-vogt.de> wrote:
> The latest kernel it seems to get stuck at
> console_lock() in register_framebuffer (drivers/video/fbmem.c:1655)
> if the LCD-controller is enabled. (Early printk and serial console works fine)
> CONFIG_NO_HZ is not activated, it works completely.
> Could this be a kernel bug or is this an issue with our timer configuration?
Even with the CONFIG_NO_HZ option disabled, I've found that probing of our LCD hardware sometimes still fail with an error of -2.
Depending on how I arrange the device tree or the contents of the boot arguments or, as said, the CONFIG_NO_HZ option, I get different behaviours ranging from:
* Getting a -2 error during device probe (possibly due to a clock not being found).
* LCD hardware is found but boot hangs right after the driver is initialised.
* LCD hardware is apparently initialised correctly and text appears onscreen but user mode init hangs and I never get to a shell prompt.
This smells of a race condition that occurs before the clcd driver even gets to initialise. Some bug in our timer code? A OF or console bug perhaps? Though, I'm a bit hesitant to blame it on a kernel subsystem bug until it's clear that our code isn't at fault.
Any suggestions?
next prev parent reply other threads:[~2013-04-09 6:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 9:01 Daniel Tang
2013-04-04 11:12 ` Arnd Bergmann
2013-04-06 0:26 ` Daniel Tang
2013-04-06 11:51 ` Arnd Bergmann
2013-04-06 12:00 ` Daniel Tang
2013-04-06 13:24 ` Arnd Bergmann
2013-04-07 0:06 ` Daniel Tang
2013-04-07 3:56 ` Daniel Tang
2013-04-07 21:23 ` Arnd Bergmann
2013-04-08 11:33 ` Daniel Tang
2013-04-08 19:16 ` Fabian Vogt
2013-04-08 19:38 ` Arnd Bergmann
2013-04-08 20:06 ` Fabian Vogt
2013-04-08 21:29 ` Arnd Bergmann
2013-04-09 5:59 ` Daniel Tang [this message]
2013-04-09 11:23 ` Linus Walleij
2013-04-09 12:01 ` Pawel Moll
2013-04-09 12:05 ` Linus Walleij
2013-04-09 13:51 ` Russell King - ARM Linux
2013-04-07 14:32 ` Arnd Bergmann
2013-04-09 11:14 ` Linus Walleij
2013-04-09 11:39 ` Daniel Tang
2013-04-09 11:58 ` 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=29D8E742-C870-45AE-B102-13A477AE6419@gmail.com \
--to=dt.tangr@gmail.com \
--cc=arnd@arndb.de \
--cc=fabian@ritter-vogt.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lionel_debroux@yahoo.fr \
/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
all inboxes | Powered by JetHome®