From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] mackerel: Do not enable TMU timer in default config
Date: Mon, 13 Feb 2012 23:33:04 +0000 [thread overview]
Message-ID: <20120213233304.GA19671@linux-sh.org> (raw)
In-Reply-To: <1329111377-15676-1-git-send-email-horms@verge.net.au>
On Mon, Feb 13, 2012 at 02:36:17PM +0900, Simon Horman wrote:
> This allows the mackerel to boot using a kernel compiled
> using the mackerel default config. Without this change
> the kernel boot hangs during or immediately after SCIF
> initialisation.
>
> SuperH SCI(F) driver initialized
> sh-sci.0: ttySC0 at MMIO 0xe6c40000 (irq = 80) is a scifa
> sh-sci sh-sci.0: start latency exceeded, new value 5416 ns
> console [ttySC0] enabled, bootconsole disabled
> console [ttySC0] enabled, bootconsole disabled
>
> Signed-off-by: Simon Horman <horms@verge.net.au>
>
> ---
>
> This resolves a regression since 3.2.
> I am unsure if there is a cleaner way to resolve this problem
> nor if other boards are affected.
That's different. Do you see the start latency exceeded thing with TMU
disabled? Perhaps there is a pinmux conflict between some of the channels
and SCIF functions, it'd be interesting to figure out what the issue is
rather than simply hiding it. You mention this as a regression, so
presumably it worked ok up until some point? Perhaps something in the
recent batch of sh-sci updates broke existing behaviour?
next prev parent reply other threads:[~2012-02-13 23:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 5:36 [PATCH] mackerel: Do not enable TMU timer in default config Simon Horman
2012-02-13 23:33 ` Paul Mundt [this message]
2012-02-14 0:35 ` Simon Horman
2012-02-23 10:06 ` Simon Horman
2012-02-23 15:30 ` Paul Mundt
2012-02-23 22:14 ` Rafael J. Wysocki
2012-02-26 22:57 ` Rafael J. Wysocki
2012-02-27 0:55 ` Simon Horman
2012-02-27 6:06 ` Paul Mundt
2012-02-27 22:30 ` Rafael J. Wysocki
2012-02-28 1:23 ` Rafael J. Wysocki
2012-02-28 1:38 ` Simon Horman
2012-02-28 6:09 ` Paul Mundt
2012-02-28 9:29 ` Simon Horman
2012-02-28 23:59 ` Rafael J. Wysocki
2012-02-29 1:32 ` Simon Horman
2012-03-02 23:27 ` Rafael J. Wysocki
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=20120213233304.GA19671@linux-sh.org \
--to=lethal@linux-sh.org \
--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.