In kgsl_ioctl_gpuobj_import(), user memory of type KGSL_USER_MEM_TYPE_ADDR
can also lead to setting up a dma buffer. When attaching mem entry to
process fails, dma buffer attachment is cleaned up only in case of
KGSL_USER_MEM_TYPE_DMABUF. Similar situation can arise in case of
kgsl_ioctl_map_user_mem(). Fix this by obtaining user memory type from
the memdesc flags.
Change-Id: I502bd0ae19241802e8f835f20391b2ce67999418
Signed-off-by: Puranam V G Tejaswi <pvgtejas@codeaurora.org>
Signed-off-by: Deepak Kumar <dkumar@codeaurora.org>
Add support for IDP and ATP hw platforms in socinfo driver.
Change-Id: Icc2a496d06e57c1869a5129b628c2d095db9186b
Signed-off-by: Yogesh Lal <ylal@codeaurora.org>
update the debug mux for Silver/Gold/L3 CPU clocks.
Change-Id: I124a998fd63e6d0b63289777890c39812d51ea5d
Signed-off-by: Taniya Das <tdas@codeaurora.org>
cpuinfo.min_freq/max_freq gives the real min/max frequencies available.
whereas policy min/max offer current min/max of the policy, which
may be the desired values set by any other client like msm_perf or
even a postboot setting. This can potentially limit min/max
frequencies ranges.
Change-Id: Ia7978ccd99b419f68d06fec24dac1adfacff36b7
Signed-off-by: Kishore Sri venkata Ganesh Bolisetty <bsrivenk@codeaurora.org>
memblock_alloc is not giving information of owner of the memblock_reserve,
when we pass through command line "memblock=debug".
Below information is not enough for memory statistics.
for example:
[ 0.000000] memblock_reserve: [0x000000013fbf8000-0x000000013fbf8fff] memblock_alloc+0x50/0x60.
To enhance the memblokc_dbg information or to get the exact owner of the
memblock_reserve added debug logs in different memblock alloc functions,
which is helpful for memory statistics.
After adding logs:
[ 0.000000] memblock_alloc: size: 4096 align: 4096 early_pgtable_alloc+0x18/0x98.
[ 0.000000] memblock_reserve: [0x000000013fbf9000-0x000000013fbf9fff] memblock_alloc+0x50/0x60.
Change-Id: Ibc9603f71fe3150af67398658d04c34f824b47e1
Signed-off-by: Faiyaz Mohammed <faiyazm@codeaurora.org>
