On Tue, Feb 07, 2012 at 12:51:42AM -0800, anish kumar wrote:

Hi,

Now I have switched to using request_firmware api
and after using firmware, memory is being released.
Does it save kernel memory compare to case when 
I am having a having a local static firmware buffer(very big)
from which I used to get the firmware and write it
to the chip?

As I know request_firmware api has several advantages
but what I want to know is the advantages related
to kernel memory footprint.

Yes it is, as well as using the "proper" api for firmware loading, which
means it fits into the rest of the kernel correctly.

Also, no new drivers will be accepted that have static firmware blobs.

greg k-h