[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130422143537.GD7508@arwen.pp.htv.fi>
Date: Mon, 22 Apr 2013 17:35:37 +0300
From: Felipe Balbi <balbi@...com>
To: Sourav Poddar <sourav.poddar@...com>
CC: <gregkh@...uxfoundation.org>, <tony@...mide.com>,
<rmk+kernel@....linux.org.uk>, <khilman@...aro.org>,
<linux-serial@...r.kernel.org>, <linux-omap@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Benoit Cousson <b-cousson@...com>,
Santosh Shilimkar <santosh.shilimkar@...com>,
Felipe Balbi <balbi@...com>, Rajendra nayak <rnayak@...com>
Subject: Re: [PATCHv2 4/5] arm: dts: am33xx: Remove "ti,no_idle_on_suspend"
property.
Hi,
On Mon, Apr 22, 2013 at 07:13:56PM +0530, Sourav Poddar wrote:
> The "ti,no_idle_on_suspend" property was required to keep ocmcram
> clocks running during idle.
>
> But the commit below[1], added in v3.6 should prevent the
> any automaic clock gating for devices without drivers bound. Since
> there is no driver for the OCM RAM block, we are not affected by
> the automatic idle on suspend anyways.
> [1]:
> commit 72bb6f9b51c82c820ddef892455a85b115460904
your commit log can be improved a bit, it could look like below:
The "ti,no_idle_on_suspend" property was required to keep ocmcram clocks
running during idle.
But commit 72bb6f9 (ARM: OMAP: omap_device: don't attempt late suspend
if no driver bound), added in v3.6 should prevent any automatic clock
gating for devices without drivers bound. Since there is no driver for
the OCM RAM block, we are not affected by the automatic idle on suspend
anyways which means "ti,no_idle_on_suspend" can be safely removed since
there are no users for it.
other than that:
Reviewed-by: Felipe Balbi <balbi@...com>
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists