Hi Tero, Rajendra, Santosh,
As we've discussed, there are known bootloader dependencies with the OMAP4
PM retention idle code, introduced in v3.8. Boards booted with u-boot
versions even as recent as 2011 won't enter retention idle correctly; for
example:
http://www.pwsan.com/omap/testl
Hi Tero et al.,
On Tue, 22 Jan 2013, Paul Walmsley wrote:
> As we've discussed, there are known bootloader dependencies with the OMAP4
> PM retention idle code, introduced in v3.8. Boards booted with u-boot
> versions even as recent as 2011 won't enter retention idle correctly; for
> example:
On Wed, 2013-01-30 at 17:15 +, Paul Walmsley wrote:
> Hi Tero et al.,
>
> On Tue, 22 Jan 2013, Paul Walmsley wrote:
>
> > As we've discussed, there are known bootloader dependencies with the OMAP4
> > PM retention idle code, introduced in v3.8. Boards booted with u-boot
> > versions even a
Tero,
On Thursday 31 January 2013 02:30 PM, Tero Kristo wrote:
Personally I don't like too much to have just extra spam during boot,
which in many cases is even unnecessary (e.g. people who actually have
good u-boot in use.) Personally I would like to have some sort of test
during boot which det
Hi,
On Thu, 31 Jan 2013, Tero Kristo wrote:
> Personally I don't like too much to have just extra spam during boot,
> which in many cases is even unnecessary (e.g. people who actually have
> good u-boot in use.)
The impact of two or three informative lines sent to the kernel console on
boot is
Hi,
On Thu, 31 Jan 2013, Rajendra Nayak wrote:
> Throw a pr_warn() at boot only when CONFIG_CPU_IDLE is enabled. Note
> that it isn't enabled by default in omap2plus_defconfig. Also
> throw one when a suspend fails, saying bootloader *could be* a possible
> cause specifying the right version to b
On Thursday 31 January 2013 09:10 PM, Paul Walmsley wrote:
Hi,
On Thu, 31 Jan 2013, Rajendra Nayak wrote:
Throw a pr_warn() at boot only when CONFIG_CPU_IDLE is enabled. Note
that it isn't enabled by default in omap2plus_defconfig. Also
throw one when a suspend fails, saying bootloader *could
Hi,
On Thu, 31 Jan 2013, Santosh Shilimkar wrote:
> On Thursday 31 January 2013 09:10 PM, Paul Walmsley wrote:
> > On Thu, 31 Jan 2013, Rajendra Nayak wrote:
> >
> > > Throw a pr_warn() at boot only when CONFIG_CPU_IDLE is enabled. Note
> > > that it isn't enabled by default in omap2plus_defconf
On Thu, 31 Jan 2013, Paul Walmsley wrote:
> Right. I don't have any problem with adding a message to the suspend path
> also. But I'd like to see a boot-time message added even if
> CONFIG_CPU_IDLE=n, since it's still possible to enter full-chip retention
> idle with dynamic idle. In other w
On Thu, 31 Jan 2013, Paul Walmsley wrote:
> On Thu, 31 Jan 2013, Paul Walmsley wrote:
>
> > Right. I don't have any problem with adding a message to the suspend path
> > also. But I'd like to see a boot-time message added even if
> > CONFIG_CPU_IDLE=n, since it's still possible to enter full-
Hi Paul,
On 01/21/2013 08:42 PM, Paul Walmsley wrote:
>
> Hi Tero, Rajendra, Santosh,
>
> As we've discussed, there are known bootloader dependencies with the OMAP4
> PM retention idle code, introduced in v3.8. Boards booted with u-boot
> versions even as recent as 2011 won't enter retention
Hi Jon,
sorry for the delay,
On Tue, 5 Feb 2013, Jon Hunter wrote:
> I noticed on my OMAP4430 SDP that in suspend L3INIT was failing to enter
> retention state. I am not sure if this is the same problem that you are
> seeing or not. However, I found that the reason the L3INIT was not entering
12 matches
Mail list logo
