linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/1] misc: sram: add dev_pm_ops to support module power gate
Date: Tue, 25 Aug 2015 14:02:54 +0100	[thread overview]
Message-ID: <55DC677E.1030004@arm.com> (raw)
In-Reply-To: <1438272681-29338-1-git-send-email-shenwei.wang@freescale.com>



On 30/07/15 17:11, Shenwei Wang wrote:
> When system goes into low power states like SUSPEND_MEM and
> HIBERNATION, the hardware IP block may be powered off to reduce
> the power consumption. This power down will lost all the
> data inside the ram. This patch added the dev_pm_ops and
> implemented two callbacks: suspend_noirq and resume_noirq, which
> will save the data in the on-chip-ram right before power down
> and restore it after system resumes.
>

Who uses this SRAM ? Can't they be released before suspending ?
This might not be feasible and time consuming as the size of SRAM increases.

Also I just check the entire tree for the users of gen_pool, I found
it's used for video/audio and crypto which needs to on-demand basis.
Apart from that it's mainly used for low power modes in which case,
SRAM needs to be powered on. So can you provide more details on your
use-case.

> A new property string named "can-power-gate" is added to
> the devicetree bindings too.
>
> Signed-off-by: Shenwei Wang <shenwei.wang@freescale.com>
> Signed-off-by: Anson Huang <b20788@freescale.com>
> ---
> Change log:
>
> PATCH v3
> 	Removed the unnecessary clk_enable/clk_disable.
>
> PATCH v2
> 	Use vmalloc to allocate the SRAM backup memory.
> 	Code clean up.
>
>   Documentation/devicetree/bindings/misc/sram.txt |  2 ++
>   drivers/misc/sram.c                             | 42 +++++++++++++++++++++++++
>   2 files changed, 44 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/misc/sram.txt b/Documentation/devicetree/bindings/misc/sram.txt
> index 36cbe5a..1170086 100644
> --- a/Documentation/devicetree/bindings/misc/sram.txt
> +++ b/Documentation/devicetree/bindings/misc/sram.txt
> @@ -33,6 +33,8 @@ Optional properties in the area nodes:
>
>   - compatible : standard definition, should contain a vendor specific string
>                  in the form <vendor>,[<device>-]<usage>
> +- can-power-gate: a property to tell the driver that the sram can support
> +		power gate
>

Please cc device-tree list for such generic bindings.

Regards,
Sudeep

  parent reply	other threads:[~2015-08-25 13:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 16:11 [PATCH v3 1/1] misc: sram: add dev_pm_ops to support module power gate Shenwei Wang
2015-08-05 21:11 ` Shenwei Wang
2015-08-12 15:47 ` Shenwei Wang
2015-08-20 14:48   ` Shenwei Wang
2015-08-24 20:26 ` Shenwei Wang
2015-08-25 13:02 ` Sudeep Holla [this message]
2015-08-25 13:47   ` Shenwei Wang
2015-08-25 13:59     ` Sudeep Holla
2015-08-25 14:20       ` Shenwei Wang
2015-08-25 14:40         ` Sudeep Holla
2015-08-25 15:05           ` Shenwei Wang
2015-08-25 16:03             ` Sudeep Holla
2015-08-25 19:35               ` Shenwei Wang
2015-08-26  9:26                 ` Sudeep Holla

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=55DC677E.1030004@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).