If a process forked and the child process was killed by the
lowmemorykiller, the lowmemory killer would be disabled until
the parent process reaped the child or it died itself.

Change-Id: I49822d847ee54876b474a837743b4f4821fba57f
Signed-off-by: Arve Hjønnevåg <arve@android.com>
Reviewed-on: http://git-master/r/15091
Reviewed-by: Ching Kuang (Roger) Hsieh <rhsieh@nvidia.com>
Tested-by: Ching Kuang (Roger) Hsieh <rhsieh@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>

The lowmemorykiller registers an atomic notifier for notfication of when
the task is freed.  From this atomic notifier callback, it removes the
atomic notifier via task_free_unregister().  This is incorrect because
atomic_notifier_chain_unregister() calls syncronize_rcu(), which can
sleep, which shouldn't be done from an atomic notifier.

Fix this by registering the notifier during init, and only unregister it
if the lowmemorykiller is unloaded.

Change-Id: Ie9cf2f23d31c78e1fe1b9dd2e11af5267832ee94
Signed-off-by: Rabin Vincent <rabin.vincent@stericsson.com>
Signed-off-by: Christian Bejram <christian.bejram@stericsson.com>
Reviewed-on: http://git-master/r/13943
Reviewed-by: Ching Kuang (Roger) Hsieh <rhsieh@nvidia.com>
Tested-by: Ching Kuang (Roger) Hsieh <rhsieh@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>

(cherry picked from commit 9dc305371bfe820db10e554e0bd8e60b16f94ab8)

Change-Id: Ie857ffa2ebdb2eec5b75bf93ae954798e74dad3f
Reviewed-on: http://git-master/r/9847
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>

This reverts commit 6469f378a596f0572035cd27a17851ea86b763c9.

Bug 758628
Bug 748669

Original commit attmpted to have a smarter cache cleaning code.
But that work didn't work out well and just resulted in display
corruption.

Reviewed-on: http://git-master/r/11817
(cherry picked from commit 60207394cc16689f06ccbac993eefd2928565031)

Change-Id: I92bd95154f372eb0a081a4c3919b87d576ea4cb5
Reviewed-on: http://git-master/r/12449
Reviewed-by: Youngjin Kim <nkim@nvidia.com>
Tested-by: Youngjin Kim <nkim@nvidia.com>
Reviewed-by: Markus Holtmanns <mholtmanns@nvidia.com>
Tested-by: Markus Holtmanns <mholtmanns@nvidia.com>
Reviewed-by: Niket Sirsi <nsirsi@nvidia.com>
Tested-by: Niket Sirsi <nsirsi@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>

Reviewed-on: http://git-master/r/10445
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
Tested-by: Yu-Huan Hsu <yhsu@nvidia.com>
(cherry picked from commit 0a4752eb037a5d4492d108ec094dd5367f5faa09)

Change-Id: I03a8224b8d3ccb4e7b0f682a75648ff9e9cda06f
Reviewed-on: http://git-master/r/11717
Reviewed-by: Robert R Collins <rcollins@nvidia.com>
Tested-by: Robert R Collins <rcollins@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>

(Cherry-Picked Panjit driver from cc8231d0ddef32343db199b6a668d572c079afc4)

Reviewed-on: http://git-master/r/10443
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
Tested-by: Yu-Huan Hsu <yhsu@nvidia.com>
(cherry picked from commit 208bbaaf873e202531e3d8045c9a5f534ba4906e)

Change-Id: Ie08bc42669fad152931be095a8a549852dd9be12
Reviewed-on: http://git-master/r/11716
Tested-by: Robert R Collins <rcollins@nvidia.com>
Reviewed-by: Robert R Collins <rcollins@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>

Bug: 730157
Change-Id: I8741f2be5c3c8933edf0dcc3b9d00006eeb86117
Reviewed-on: http://git-master/r/11682
Reviewed-by: Rahul Bansal <rbansal@nvidia.com>
Tested-by: Rahul Bansal <rbansal@nvidia.com>
Reviewed-by: Rakesh Kumar <krakesh@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>

The requested SD clock will be limited to the maximum
supported clock on the platform.

Bug 761966

Change-Id: I03cd76ae42f56675f47d185da73352e716f6d255
Reviewed-on: http://git-master/r/11429
Tested-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>

For large allocations, cleaning each page of the allocation can
take a significant amount of time. If an allocation that nvmap needs
to clean or invalidate out of the cache is significantly larger than
the cache, just flush the entire cache.

bug 711478 and bug 744221

Revert "video: tegra: nvmap: perform cache maintenance for rw_handle"

This reverts commit d963f09c3ebb2d690d266f8f607b4876acaf2ab1.

Reviewed-on: http://git-master/r/10213
(cherry picked from commit 6469f378a596f0572035cd27a17851ea86b763c9)

Change-Id: I1e514f505db860eb01d575a98f0f80c8794e8463
Reviewed-on: http://git-master/r/10497
Reviewed-by: Eric Werness <ewerness@nvidia.com>
Reviewed-by: Markus Holtmanns <mholtmanns@nvidia.com>
Tested-by: Markus Holtmanns <mholtmanns@nvidia.com>
Reviewed-by: Janne Hellsten <jhellsten@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>

Getting the transfer count by dma with rts disable. In this way
we can avoid the race condition arise by hw with incoming data.

Change-Id: Ieeeadfeea9293c70fd2eb96ff9d82888a58b2b3a
Reviewed-on: http://git-master/r/11020
Tested-by: Rakesh Goyal <rgoyal@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Udaykumar Rameshchan Raval <uraval@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>