[PATCH v3 1/1] misc: sram: add dev_pm_ops to support module power gate
sudeep.holla at arm.com
Tue Aug 25 07:40:30 PDT 2015
On 25/08/15 15:20, Shenwei Wang wrote:
>> -----Original Message-----
>> From: Sudeep Holla [mailto:sudeep.holla at arm.com]
>> Sent: 2015年8月25日 9:00
>> To: Wang Shenwei-B38339
>> Cc: Sudeep Holla; gregkh at linuxfoundation.org; arnd at arndb.de; Huang
>> Yongcai-B20788; linux-arm-kernel at lists.infradead.org
>> Subject: Re: [PATCH v3 1/1] misc: sram: add dev_pm_ops to support module
>> power gate
>>> On latest Freescale i.MX7D, it has two SRAMs in side. One is for low
>>> power mode which will be powered on in suspend state. The other one is
>>> for other peripherals which can be powered off on demand.
>> What I meant is who will be using the SRAM when entering S2R that you need to
>> save the content. Either the user needs to take care of the content or just release
>> the pool when not in use. When the sram pool has no user, clock can be gated.
>> Again can you give details of this use-case.
> We are not talking about clock gate state. Here we are handling the power gate for
> this SRAM IP block. Of course, you can ask each driver to save its contents during
> low power state, but I think the easier way is to save the contents in this sram driver
> and just leave the drivers who use this sram behave as is today.
I don't like that solution as it's not scalable with SRAM size and
saving all the content of SRAM just because of few active regions makes
no sense to me at-least. I prefer leaving it to the users to handle that
rather than SRAM driver.
More information about the linux-arm-kernel