All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Yegor Yefremov <yegor_sub1@visionsystems.de>
Cc: "Mark A. Greer" <mgreer@animalcreek.com>,
	Kevin Hilman <khilman@linaro.org>, Paul Walmsley <paul@pwsan.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP3: Fix iva2_pwrdm settings for 3703
Date: Thu, 16 May 2013 11:54:44 -0700	[thread overview]
Message-ID: <20130516185444.GK5600@atomide.com> (raw)
In-Reply-To: <20130516183516.GJ5600@atomide.com>

* Tony Lindgren <tony@atomide.com> [130516 11:40]:
> * Yegor Yefremov <yegor_sub1@visionsystems.de> [130516 05:13]:
> > 
> > I think this issue is relevant to am3517 as you can see from this thread: http://thread.gmane.org/gmane.linux.ports.arm.omap/97903
> > I could boot only with your patch http://www.spinics.net/lists/arm-kernel/msg168865.html
> 
> OK sounds like Mark's patch as http://www.spinics.net/lists/arm-kernel/msg168865.html
> is needed as a fix.

Yegor, thinking about your boot issue more, I'm thinking that you
have your board .init_time = omap3_secure_sync32k_timer_init, or
some non-waking gpt timer. And that means the system won't wake to
timer events.

The system should still wake to timer events even if you have no
wake-up events configred, so Mark's patch probably does not fix
the right issue for you.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP3: Fix iva2_pwrdm settings for 3703
Date: Thu, 16 May 2013 11:54:44 -0700	[thread overview]
Message-ID: <20130516185444.GK5600@atomide.com> (raw)
In-Reply-To: <20130516183516.GJ5600@atomide.com>

* Tony Lindgren <tony@atomide.com> [130516 11:40]:
> * Yegor Yefremov <yegor_sub1@visionsystems.de> [130516 05:13]:
> > 
> > I think this issue is relevant to am3517 as you can see from this thread: http://thread.gmane.org/gmane.linux.ports.arm.omap/97903
> > I could boot only with your patch http://www.spinics.net/lists/arm-kernel/msg168865.html
> 
> OK sounds like Mark's patch as http://www.spinics.net/lists/arm-kernel/msg168865.html
> is needed as a fix.

Yegor, thinking about your boot issue more, I'm thinking that you
have your board .init_time = omap3_secure_sync32k_timer_init, or
some non-waking gpt timer. And that means the system won't wake to
timer events.

The system should still wake to timer events even if you have no
wake-up events configred, so Mark's patch probably does not fix
the right issue for you.

Regards,

Tony

  reply	other threads:[~2013-05-16 18:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15  0:25 [PATCH] ARM: OMAP3: Fix iva2_pwrdm settings for 3703 Tony Lindgren
2013-05-15  1:52 ` Mark A. Greer
2013-05-15 17:07   ` Tony Lindgren
2013-05-15 17:07     ` Tony Lindgren
2013-05-15 21:50     ` Mark A. Greer
2013-05-15 21:50       ` Mark A. Greer
2013-05-16 10:19       ` Yegor Yefremov
2013-05-16 10:19         ` Yegor Yefremov
2013-05-16 18:35         ` Tony Lindgren
2013-05-16 18:35           ` Tony Lindgren
2013-05-16 18:54           ` Tony Lindgren [this message]
2013-05-16 18:54             ` Tony Lindgren
2013-05-17 18:47           ` Mark A. Greer
2013-05-17 18:47             ` Mark A. Greer
2013-05-17 18:56         ` Mark A. Greer
2013-05-17 18:56           ` Mark A. Greer
2013-05-17 21:28           ` Yegor Yefremov
2013-05-17 21:28             ` Yegor Yefremov
2013-05-20 22:05             ` Tony Lindgren
2013-05-20 22:05               ` Tony Lindgren
2013-05-21  9:17               ` Yegor Yefremov
2013-05-21  9:17                 ` Yegor Yefremov
2013-05-21 15:56               ` Mark A. Greer
2013-05-21 15:56                 ` Mark A. Greer
2013-05-21 18:20               ` Kevin Hilman
2013-05-21 18:20                 ` Kevin Hilman
2013-05-22  8:09                 ` Yegor Yefremov
2013-05-22  8:09                   ` Yegor Yefremov
2013-05-17 21:05   ` Mark A. Greer

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=20130516185444.GK5600@atomide.com \
    --to=tony@atomide.com \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mgreer@animalcreek.com \
    --cc=paul@pwsan.com \
    --cc=yegor_sub1@visionsystems.de \
    /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.