linux.git/drivers/gpu/drm/msm, branch v4.13-rc2

drm/msm: Fix potential buffer overflow issue

2017-06-19T23:58:57+00:00

In function submit_create, if nr_cmds or nr_bos is assigned with
negative value, the allocated buffer may be small than intended.
Using this buffer will lead to buffer overflow issue.

Signed-off-by: Kasin Li 
Signed-off-by: Jordan Crouse 
Signed-off-by: Rob Clark

drm/msm: Separate locking of buffer resources from struct_mutex

2017-06-17T12:03:07+00:00

Buffer object specific resources like pages, domains, sg list
need not be protected with struct_mutex. They can be protected
with a buffer object level lock. This simplifies locking and
makes it easier to avoid potential recursive locking scenarios
for SVM involving mmap_sem and struct_mutex. This also removes
unnecessary serialization when creating buffer objects, and also
between buffer object creation and GPU command submission.

Signed-off-by: Sushmita Susheelendra 
[robclark: squash in handling new locking for shrinker]
Signed-off-by: Rob Clark

drm/msm/hdmi: Fix HDMI pink strip issue seen on 8x96

2017-06-16T15:16:09+00:00

A 2 pixel wide pink strip was observed on the left end of some HDMI
monitors configured in a HDMI mode.

It turned out that we were missing out on configuring AVI infoframes, and
unlike APQ8064, the 8x96 HDMI H/W seems to be sensitive to that.

Add configuration of AVI infoframes. While at it, make sure that
hdmi_audio_update is only called when we've detected that the monitor
supports HDMI.

Signed-off-by: Archit Taneja 
Signed-off-by: Rob Clark

drm/msm/hdmi: 8996 PLL: Populate unprepare

2017-06-16T15:16:08+00:00

Without doing anything in unprepare, the HDMI driver isn't able to
switch modes successfully. Calling set_rate with a new rate results
in an un-locked PLL.

If we reset the PLL in unprepare, the PLL is able to lock with the
new rate.

Signed-off-by: Archit Taneja 
Signed-off-by: Rob Clark

drm/msm/hdmi: Use bitwise operators when building register values

2017-06-16T15:16:08+00:00

Commit c0c0d9eeeb8d ("drm/msm: hdmi audio support") uses logical
OR operators to build up a value to be written in the
REG_HDMI_AUDIO_INFO0 and REG_HDMI_AUDIO_INFO1 registers when it
should have used bitwise operators.

Signed-off-by: Liviu Dudau 
Fixes: c0c0d9eeeb8d ("drm/msm: hdmi audio support")
Signed-off-by: Rob Clark

drm/msm: update generated headers

2017-06-16T15:16:07+00:00

Signed-off-by: Rob Clark

drm/msm: remove address-space id

2017-06-16T15:16:06+00:00

Now that the msm_gem supports an arbitrary number of vma's, we no longer
need to assign an id (index) to each address space.  So rip out the
associated code.

Signed-off-by: Rob Clark

drm/msm: support for an arbitrary number of address spaces

2017-06-16T15:16:06+00:00

It means we have to do a list traversal where we once had an index into
a table.  But the list will normally have one or two entries.

Signed-off-by: Rob Clark

drm/msm: refactor how we handle vram carveout buffers

2017-06-16T15:16:05+00:00

Pull some of the logic out into msm_gem_new() (since we don't need to
care about the imported-bo case), and don't defer allocating pages.  The
latter is generally a good idea, since if we are using VRAM carveout to
allocate contiguous buffers (ie. no IOMMU), the allocation is more
likely to fail.  So failing at allocation time is a more sane option.
Plus this simplifies things in the next patch.

Signed-off-by: Rob Clark

drm/msm: pass address-space to _get_iova() and friends

2017-06-16T15:16:04+00:00

No functional change, that will come later.  But this will make it
easier to deal with dynamically created address spaces (ie. per-
process pagetables for gpu).

Signed-off-by: Rob Clark