kgsl: add interactive algorithm merged from my changes on mako FK.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>

Conflicts:

	drivers/gpu/msm/kgsl_pwrscale_trustzone.c
kgsl: scale up_threshold based on the active_pwrlevel so that the algorithm uses 200MHz step more often while the user is scrolling or just loading apps that require a bit of GPU power.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
\kgsl: add back content to the sleep function for this tz routine. Also fix the length of the governor name for the sysfs entry.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
kgsl: lets add a struct to keep some stats because... I like structs, and looks tidy. Now the point was to keep global variables because I don't want the kgsl sleep routine to kick in and lower the GPU frequency to the minimum if the GPU load is greater than down_threshold. Since the polling is so fast this won't do any harm, but quite the contrary it will help maintaining the FPS.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
kgsl: disable DEBUG flag.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
sync: don't block the flusher thread waiting on IO

When sync does it's WB_SYNC_ALL writeback, it issues data Io and
then immediately waits for IO completion. This is done in the
context of the flusher thread, and hence completely ties up the
flusher thread for the backing device until all the dirty inodes
have been synced. On filesystems that are dirtying inodes constantly
and quickly, this means the flusher thread can be tied up for
minutes per sync call and hence badly affect system level write IO
performance as the page cache cannot be cleaned quickly.

We already have a wait loop for IO completion for sync(2), so cut
this out of the flusher thread and delegate it to wait_sb_inodes().
Hence we can do rapid IO submission, and then wait for it all to
complete.

Effect of sync on fsmark before the patch:

FSUse%        Count         Size    Files/sec     App Overhead
.....
     0       640000         4096      35154.6          1026984
     0       720000         4096      36740.3          1023844
     0       800000         4096      36184.6           916599
     0       880000         4096       1282.7          1054367
     0       960000         4096       3951.3           918773
     0      1040000         4096      40646.2           996448
     0      1120000         4096      43610.1           895647
     0      1200000         4096      40333.1           921048

And a single sync pass took:

  real    0m52.407s
  user    0m0.000s
  sys     0m0.090s

After the patch, there is no impact on fsmark results, and each
individual sync(2) operation run concurrently with the same fsmark
workload takes roughly 7s:

  real    0m6.930s
  user    0m0.000s
  sys     0m0.039s

IOWs, sync is 7-8x faster on a busy filesystem and does not have an
adverse impact on ongoing async data write operations.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
kgsl_pwrscale_trustzone: fix build
qseecom: Fix issue with incomplete command exiting prematurely

A process waiting on a signal can be awaken by any signal. We
need to only continue processing when the condition of the
wait event is met.

Change-Id: Ib2102babbb505876f89b04399729e6ff5a475605
Signed-off-by: Mona Hossain <mhossain@codeaurora.org>
Signed-off-by: Praveen Chavan <pchavan@codeaurora.org>
v2.0.1