public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: Paul Walmsley <paul@pwsan.com>, tony@atomide.com
Cc: nm@ti.com, j-keerthy@ti.com, t-kristo@ti.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: DRA7: hwmod: Fix GPMC from preventing core suspend
Date: Wed, 3 Jun 2015 13:51:33 +0300	[thread overview]
Message-ID: <556EDC35.2060101@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1506022135000.14902@utopia.booyaka.com>

Paul,

On 03/06/15 00:36, Paul Walmsley wrote:
> On Tue, 2 Jun 2015, Roger Quadros wrote:
>
>> GPMC hwmod is flagged as HWMOD_INIT_NO_IDLE so it is kept
>> enabled at boot. If the GPMC driver is not loaded then
>> GPMC will not be idled thus preventing CORE from going idle
>> during suspend.
>>
>> Disable HWMOD_INIT_NO_IDLE and HWMOD_INIT_NO_RESET.
>>
>> The only reason HWMOD_INIT_NO_RESET was there was to retain
>> GPMC timings/settings configured by bootloader. We no longer
>> need that as we're configuring the timins in the kernel.
>>
>> There is no reasoning as to why HWMOD_INIT_NO_IDLE was there.
>> Seems to have beein blindly copied from omap3/4 hwmod code.
>>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>
> Hi Roger, could you take a look at Tony's patch "memory: omap-gpmc: Add
> Kconfig option for debug" and see if this needs to be changed in light of
> that patch?

Yes. We don't need this patch if we can just rid of HWMOD_SWSUP_SIDLE
as done in the first patch.

cheers,
-roger

      reply	other threads:[~2015-06-03 10:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 10:02 [PATCH 0/2] ARM: DRA7: hwmod: fix gpmc hwmod for core-retention Roger Quadros
2015-06-02 10:02 ` [PATCH 1/2] ARM: DRA7: hwmod: fix gpmc hwmod Roger Quadros
2015-06-02 21:34   ` Paul Walmsley
2015-06-10 12:44     ` Roger Quadros
2015-06-03 12:38   ` [PATCH v2 1/1] " Roger Quadros
2015-06-02 10:02 ` [PATCH 2/2] ARM: DRA7: hwmod: Fix GPMC from preventing core suspend Roger Quadros
2015-06-02 21:36   ` Paul Walmsley
2015-06-03 10:51     ` Roger Quadros [this message]

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=556EDC35.2060101@ti.com \
    --to=rogerq@ti.com \
    --cc=j-keerthy@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=paul@pwsan.com \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.com \
    /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