[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RMK, On 03-Apr-12 1:00 PM, Russell King - ARM Linux wrote:
We don't want to do a kmalloc and flush, we want to do something similar to how OMAP4 does, keeping aside a chunk of RAM for saving the contents. But my only concern what willOn Tue, Apr 03, 2012 at 09:34:03AM +0530, Taniya Das wrote:I have a requirement where I need around ~100 bytes of memory to save contents of registers to a non-cached area before going into low power mode. I did do some analysis on a 1GB RAM device of allocating 8 bytes using the API and the below was the result was showing allocating only 8 bytes. API used : - arm_memblock_steal(SZ_8, SZ_64K);--> physical address returned is 0x3b1f0000It's silly to use this for the above purpose. Why not just use kmalloc and cache flushing to ensure that the data is pushed out to RAM?
be the minimum amount of memory allocated by arm_memblock_steal?
Also is this API advisable for devices with low system RAM?No.
-- Thanks& Regards, Taniya Das. Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html