From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM: omap[34]: Thumb-2 compatibility fixes
Date: Fri, 4 Feb 2011 16:15:03 +0530 [thread overview]
Message-ID: <36192288611a2912eca9abc99a4353ff@mail.gmail.com> (raw)
In-Reply-To: <1296756161-26092-1-git-send-email-dave.martin@linaro.org>
Dave,
> -----Original Message-----
> From: Dave Martin [mailto:dave.martin at linaro.org]
> Sent: Thursday, February 03, 2011 11:33 PM
> To: linux-arm-kernel at lists.infradead.org
> Cc: Dave Martin; Tony Lindgren; Santosh Shilimkar; Jean Pihet;
> linux-omap at vger.kernel.org; Nicolas Pitre
> Subject: [PATCH v2 0/5] ARM: omap[34]: Thumb-2 compatibility fixes
>
> This set of patches, along with some other patches under
> discussion on alkml, should enable omap3 and omap4 kernels to be
> built with CONFIG_THUMB2_KERNEL.
>
> This patch set builds on recent cleanup done by the omap
> maintainers.
>
> It is also more aggressive than my last post: all affected
> low-level code is now built in Thumb-2. At least some of this
> code definitely works, but whether the Secure firmware can talk
> to Thumb-2 code properly is unproven:
> in particular, I could use some help/advice from the omap
> community for validating that the low-level power management
> interactions actually work with this patch set.
>
> I've done simple "does it boot?" testing by building a single
> kernel with CONFIG_SMP_ON_UP and CONFIG_THUMB2_KERNEL enabled
> which works on Beagle xM A2 and Panda A1.
I have boot tested this series on OMAP3430 and OMAP4430. Also
tested the RETENTION and OFF mode in suspend on OMAP3.
I couldn't test the DVFS because it isn't in mainline yet
but the changes doesn't looks to break anything.
So if you like, you can add
Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>
> The patches can be found, along with a buildable working tree,
> in the following repo:
>
> git://git.linaro.org/people/dmart/linux-2.6-arm.git
>
> * arm/omap-thumb2: has the patches proposed here
> * arm/omap-thumb2+merged: additionally has some patches cherry-
> picked from other trees which are needed in order for the
> patches on arm/omap-thumb2 to work usefully.
> * dirty/arm/omap-thumb2+merged: buildable test tree, which adds
> 2 local patches to work around a toolchain bug.
>
> A working kernel config for this tree is here:
> http://people.linaro.org/~dmart/arm_omap-thumb2+v2_config :
>
> CONFIG_SMP_ON_UP=y
> CONFIG_THUMB2_KERNEL=y
> CONFIG_SERIAL_OMAP=n (to avoid garbage on xM; for Panda use
> console=ttyS2)
>
> (The config is derived from the linaro omap config and so turns on
> loads of modules -- don't feel you have to build them all...)
>
>
> Cherry-picked patches originated from Russell's devel tree
> and Tony Lindgren's omap-testing tree:
>
> http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-
> arm.git devel
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-
> 2.6.git omap-testing
>
>
> Dave Martin (5):
> ARM: omap4: Correct definition of do_wfi() for
> CONFIG_THUMB2_KERNEL
> ARM: omap4: Convert END() to ENDPROC() for correct linkage with
> CONFIG_THUMB2_KERNEL
> ARM: omap3: Remove hand-encoded SMC instructions
> ARM: omap3: Thumb-2 compatibility for sram34xx.S
> ARM: omap3: Thumb-2 compatibility for sleep34xx.S
>
> arch/arm/mach-omap2/include/mach/omap4-common.h | 5 ++
> arch/arm/mach-omap2/omap-headsmp.S | 2 +-
> arch/arm/mach-omap2/omap44xx-smc.S | 8 ++--
> arch/arm/mach-omap2/sleep34xx.S | 56
> ++++++++++++++++-------
> arch/arm/mach-omap2/sram34xx.S | 28 ++++++++---
> 5 files changed, 69 insertions(+), 30 deletions(-)
next prev parent reply other threads:[~2011-02-04 10:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 18:02 [PATCH v2 0/5] ARM: omap[34]: Thumb-2 compatibility fixes Dave Martin
2011-02-03 18:02 ` [PATCH v2 1/5] ARM: omap4: Correct definition of do_wfi() for CONFIG_THUMB2_KERNEL Dave Martin
2011-02-03 18:39 ` Santosh Shilimkar
2011-02-03 19:07 ` Russell King - ARM Linux
2011-02-03 19:30 ` [PATCH v2 1/5] ARM: omap4: Correct definition of do_wfi() forCONFIG_THUMB2_KERNEL Santosh Shilimkar
2011-02-04 10:58 ` Dave Martin
2011-02-04 11:18 ` Santosh Shilimkar
2011-02-03 18:02 ` [PATCH v2 2/5] ARM: omap4: Convert END() to ENDPROC() for correct linkage with CONFIG_THUMB2_KERNEL Dave Martin
2011-02-03 18:02 ` [PATCH v2 3/5] ARM: omap3: Remove hand-encoded SMC instructions Dave Martin
2011-02-03 18:38 ` Santosh Shilimkar
2011-02-03 18:02 ` [PATCH v2 4/5] ARM: omap3: Thumb-2 compatibility for sram34xx.S Dave Martin
2011-02-03 18:42 ` Santosh Shilimkar
2011-02-03 18:02 ` [PATCH v2 5/5] ARM: omap3: Thumb-2 compatibility for sleep34xx.S Dave Martin
2011-02-03 18:47 ` Santosh Shilimkar
2011-02-10 22:17 ` Kevin Hilman
2011-02-11 0:07 ` Kevin Hilman
2011-02-11 13:49 ` Dave Martin
2011-02-11 9:43 ` Dave Martin
2011-02-04 10:45 ` Santosh Shilimkar [this message]
2011-02-04 11:02 ` [PATCH v2 0/5] ARM: omap[34]: Thumb-2 compatibility fixes Dave Martin
2011-02-04 11:16 ` Santosh Shilimkar
2011-02-04 11:18 ` Dave Martin
2011-02-04 16:41 ` Dave Martin
2011-02-08 17:40 ` Dave Martin
2011-02-09 5:45 ` Santosh Shilimkar
2011-02-09 9:49 ` Dave Martin
2011-02-10 21:38 ` Kevin Hilman
2011-02-11 9:36 ` Dave Martin
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=36192288611a2912eca9abc99a4353ff@mail.gmail.com \
--to=santosh.shilimkar@ti.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).