From: Roger Quadros <rogerq@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>, tony@atomide.com
Cc: nm@ti.com, balbi@ti.com, george.cherian@ti.com, nsekhar@ti.com,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] phy: ti-pipe3: Disable clocks on system suspend
Date: Mon, 12 Jan 2015 11:21:51 +0200 [thread overview]
Message-ID: <54B3922F.3010501@ti.com> (raw)
In-Reply-To: <54AFDE4A.2000205@ti.com>
Kishon,
On 09/01/15 15:57, Kishon Vijay Abraham I wrote:
> Hi Roger,
>
> On Friday 19 December 2014 05:35 PM, Roger Quadros wrote:
>> On system suspend, the runtime_suspend() driver hook doesn't get
>> called and so the clocks are not disabled in the driver.
>> This causes the L3INIT_960M_GFCLK and L3INIT_480M_GFCLK to remain
>> active on the DRA7 platform while in system suspend.
>>
>> Add suspend/resume hooks to the driver.
>> In case of pcie-phy, the runtime_suspend hook gets called after
>
> This contradicts with the first line of your commit message. Is pcie-phy driver
> is an exception?
Yes in the pcie-phy case it behaves differently. I'll rewrite the message.
cheers,
-roger
>
> Thanks
> Kishon
>
>> the suspend hook so we introduce a flag phy->enabled to keep
>> track if our clocks are enabled or not to prevent multiple
>> enable/disables.
>>
>> Move enabling/disabling clock code into helper functions.
>>
>> Reported-by: Nishant Menon <nm@ti.com>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
WARNING: multiple messages have this Message-ID (diff)
From: Roger Quadros <rogerq@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>, <tony@atomide.com>
Cc: <nm@ti.com>, <balbi@ti.com>, <george.cherian@ti.com>,
<nsekhar@ti.com>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] phy: ti-pipe3: Disable clocks on system suspend
Date: Mon, 12 Jan 2015 11:21:51 +0200 [thread overview]
Message-ID: <54B3922F.3010501@ti.com> (raw)
In-Reply-To: <54AFDE4A.2000205@ti.com>
Kishon,
On 09/01/15 15:57, Kishon Vijay Abraham I wrote:
> Hi Roger,
>
> On Friday 19 December 2014 05:35 PM, Roger Quadros wrote:
>> On system suspend, the runtime_suspend() driver hook doesn't get
>> called and so the clocks are not disabled in the driver.
>> This causes the L3INIT_960M_GFCLK and L3INIT_480M_GFCLK to remain
>> active on the DRA7 platform while in system suspend.
>>
>> Add suspend/resume hooks to the driver.
>> In case of pcie-phy, the runtime_suspend hook gets called after
>
> This contradicts with the first line of your commit message. Is pcie-phy driver
> is an exception?
Yes in the pcie-phy case it behaves differently. I'll rewrite the message.
cheers,
-roger
>
> Thanks
> Kishon
>
>> the suspend hook so we introduce a flag phy->enabled to keep
>> track if our clocks are enabled or not to prevent multiple
>> enable/disables.
>>
>> Move enabling/disabling clock code into helper functions.
>>
>> Reported-by: Nishant Menon <nm@ti.com>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
next prev parent reply other threads:[~2015-01-12 9:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 12:05 [PATCH 0/2] phy: ti-pipe3: fixes for 3.19-rc Roger Quadros
2014-12-19 12:05 ` Roger Quadros
2014-12-19 12:05 ` [PATCH 1/2] phy: ti-pipe3: Disable clocks on system suspend Roger Quadros
2014-12-19 12:05 ` Roger Quadros
2015-01-09 13:57 ` Kishon Vijay Abraham I
2015-01-09 13:57 ` Kishon Vijay Abraham I
2015-01-12 9:21 ` Roger Quadros [this message]
2015-01-12 9:21 ` Roger Quadros
2014-12-19 12:05 ` [PATCH 2/2] phy: ti-pipe3: Fix SATA across suspend/resume Roger Quadros
2014-12-19 12:05 ` Roger Quadros
2014-12-22 13:52 ` Kishon Vijay Abraham I
2014-12-22 13:52 ` Kishon Vijay Abraham I
[not found] ` <5498221C.6010701-l0cyMroinI0@public.gmane.org>
2014-12-29 9:53 ` Roger Quadros
2014-12-29 9:53 ` Roger Quadros
2015-01-08 11:17 ` [PATCH v2 " Roger Quadros
2015-01-08 11:17 ` Roger Quadros
2015-01-09 13:59 ` Kishon Vijay Abraham I
2015-01-09 13:59 ` Kishon Vijay Abraham I
2015-01-12 9:23 ` Roger Quadros
2015-01-12 9:23 ` Roger Quadros
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=54B3922F.3010501@ti.com \
--to=rogerq@ti.com \
--cc=balbi@ti.com \
--cc=george.cherian@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@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 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.