drm/msm/mdp5: Find correct node for creating gem address space
authorJeffrey Hugo <jeffrey.l.hugo@gmail.com>
Mon, 8 Jul 2019 15:12:24 +0000 (08:12 -0700)
committerRob Clark <robdclark@chromium.org>
Tue, 3 Sep 2019 23:16:58 +0000 (16:16 -0700)
commit518304cbf3b2452e1e592e06bed65baced0a530d
treeb3e4c78fb3debbd043cce685ef88f4401207fe45
parentadd5bff4aa769108d05fbef0240000e7334a33b9
drm/msm/mdp5: Find correct node for creating gem address space

Creating the msm gem address space requires a reference to the dev where
the iommu is located.  The driver currently assumes this is the same as
the platform device, which breaks when the iommu is outside of the
platform device (ie in the parent).  Default to using the platform device,
but check to see if that has an iommu reference, and if not, use the parent
device instead.  This should handle all the various iommu designs for
mdp5 supported systems.

Signed-off-by: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Tested-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Rob Clark <robdclark@chromium.org>
drivers/gpu/drm/msm/disp/mdp5/mdp5_kms.c