From: Kevin Hilman <khilman@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Dave Martin <dave.martin@arm.com>,
linux-arm-kernel@lists.infradead.org, tyler.baker@linaro.org
Subject: Re: [RFC] Fix omap3 booting with thumb2 compiled kernel
Date: Wed, 27 May 2015 15:19:10 -0700 [thread overview]
Message-ID: <7h7frtmzoh.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20150527215545.GA30984@atomide.com> (Tony Lindgren's message of "Wed, 27 May 2015 14:55:46 -0700")
[ fix email for Dave Martin, +Tyler ]
Tony Lindgren <tony@atomide.com> writes:
> The power management related assembly needs to interact with
> ARM mode bootrom code, so we need to keep most of the related
> assembly in ARM mode.
>
> Currently we are entering into and ARM mode assembly function
> from thumb2 mode, so we need to make sure we switch to ARM
> mode. And we need to do that again after the cache flush.
>
> ---
>
> Kevin told me about this earlier today..
And for full boot log/panics, see the kernelci.org thumb2 kernel boots
that fail: http://kernelci.org/boot/?THUMB2_KERNEL&fail
> Anybody got better ideas for a fix here?
FWIW, a quick test of this patch makes my omap3-beagle-xm pass a simple
boot test, but it fails with off idle.
Kevin
next prev parent reply other threads:[~2015-05-27 22:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 21:55 [RFC] Fix omap3 booting with thumb2 compiled kernel Tony Lindgren
2015-05-27 22:19 ` Kevin Hilman [this message]
2015-05-27 22:55 ` Tony Lindgren
2015-05-27 23:19 ` Kevin Hilman
2015-05-28 11:43 ` Grazvydas Ignotas
2015-05-28 14:21 ` Tony Lindgren
2015-05-28 16:17 ` Dave Martin
2015-05-28 16:36 ` Tony Lindgren
2015-05-28 17:31 ` Dave Martin
2015-05-28 18:55 ` Arnd Bergmann
2015-05-28 20:41 ` Tony Lindgren
2015-05-29 11:06 ` Dave P Martin
2015-05-29 16:28 ` Tony Lindgren
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=7h7frtmzoh.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=arnd@arndb.de \
--cc=dave.martin@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=tyler.baker@linaro.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).