linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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:46:57 +0530	[thread overview]
Message-ID: <9ae36f6f04c9c1cf58fb4938dc78d6bf@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=sPeQPfcGzrLSB=9-V805y6pnU4gA5QgqMSwWe@mail.gmail.com>

> -----Original Message-----
> From: Dave Martin [mailto:dave.martin at linaro.org]
> Sent: Friday, February 04, 2011 4:33 PM
> To: Santosh Shilimkar
> Cc: linux-arm-kernel at lists.infradead.org; Tony Lindgren; Jean Pihet-
> XID; linux-omap at vger.kernel.org; Nicolas Pitre
> Subject: Re: [PATCH v2 0/5] ARM: omap[34]: Thumb-2 compatibility
> fixes
>
> On Fri, Feb 4, 2011 at 10:45 AM, Santosh Shilimkar
> <santosh.shilimkar@ti.com> wrote:
> > 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.
>
> Which tree did you use to test this?  It didn't seem to work for me
> --
> sometimes the system wouldn't suspend, complaining about USB suspend
> errors; and other times I couldn't bring it out of suspend (by
> poking
> a USB input device).
>
> I might be doing something wrong...
>
I should have mentioned this.
Used Kevins pm branch to test these features.
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git


> > 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>
> >
>
> Thanks, that's great.
>
> If there some other tree with DVFS working which I could try?  Even
> if
> these patches don't apply, I may be able to test whether the changes
> should work.
>
DVFS support is getting added and one series was posted by Vishwa.
The link for the same is :
http://www.spinics.net/lists/linux-omap/msg44393.html

Regards,
Santosh

  reply	other threads:[~2011-02-04 11:16 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 ` [PATCH v2 0/5] ARM: omap[34]: Thumb-2 compatibility fixes Santosh Shilimkar
2011-02-04 11:02   ` Dave Martin
2011-02-04 11:16     ` Santosh Shilimkar [this message]
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=9ae36f6f04c9c1cf58fb4938dc78d6bf@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).