drm/msm: drop unnecessary set_need_resched()

This was inherited from i915/udl, and not actually needed.

Signed-off-by: Rob Clark <robdclark@gmail.com>
drm backport from v3.12-rc1

Sync to commit:

commit 272b98c6455f00884f0350f775c5342358ebb73f
Author:     Linus Torvalds <torvalds@linux-foundation.org>
AuthorDate: Mon Sep 16 16:17:51 2013 -0400
Commit:     Linus Torvalds <torvalds@linux-foundation.org>
CommitDate: Mon Sep 16 16:17:51 2013 -0400

    Linux 3.12-rc1

Signed-off-by: Rob Clark <robdclark@gmail.com>
mach-msm/8960: add support for 1024x768
WIP: drm/msm: add rd logging debugfs

To ease debugging, add debugfs file which can be cat/tail'd to log
submits, along with fence #.  If GPU hangs, you can look at 'gpu'
debugfs file to find last completed fence and current register state,
and compare with logged rd file to narrow down the DRAW_INDX which
triggered the GPU hang.

Conflicts:
	drivers/gpu/drm/msm/msm_gpu.c
WIP: drm/msm: add perf logging debugfs
HACK iommu_map_range seems to be worth a few fps in xonotic..

This API doesn't exist upstream.. and well, we really even want more
than this.  We want to be able to do multiple map/unmap and then at the
end flush tlb.
WIP: drm/msm: add trace points
WIP: drm/msm: rework inactive-work

Re-arrange things a bit so that we can get work requested after a bo
fence passes, like pageflip, done before retiring bo's.  Without any
sort of bo cache in userspace, some games can trigger hundred's of
transient bo's, which can cause retire to take a long time (5-10ms).

We really need a MADVISE type mechanism so userspace can cache bo's to
reuse for new allocations, but it doesn't hurt to make sure we do things
like pageflips earlier.
WIP: perf/timechart: support for GPU

Show GPU as another "CPU" on the timeline, so we can see where it is
busy and idle.  Also show pending flips (green bar on the GPU), as well
as places where processes are blocked on a fence (yellow bar on the
process).

Currently a bit hacky.  And looking for drm/msm specific traces.  We
should probably make a set of generic traces that can be used by all drm
drivers, and use these trace events in perf.  (For other GPU's we
probably want a way to be able to visualize activity on multiple rings.)
arch/arm: fix for ww_mutex vs non-debug kernel builds

Signed-off-by: Rob Clark <robdclark@gmail.com>