Android / Etnaviv / i.MX6 update

[Lucas Stach]

Am Mittwoch, den 01.08.2018, 17:03 +0200 schrieb Martin Fuzzey:
> Hi Shawn,
> 
> On 01/08/18 05:28, Shawn Guo wrote:
> > 
> > I haven't got it all work, but the first thing I see different from
> > your side report is that, display is /dev/dri/card0 while gpu is
> > /dev/dri/card1.
> > 
> > > > [    2.828929] imx-drm display-subsystem: parent device of /soc/aips-bus at 02000000/ldb/lvds-channel at 1 is not available
> > > > [    2.839516] imx-drm display-subsystem: parent device of /soc/aips-bus at 02000000/ldb/lvds-channel at 1 is not available
> > > > [    2.850108] imx-drm display-subsystem: parent device of /soc/aips-bus at 02000000/ldb/lvds-channel at 1 is not available
> > > > [    2.860681] imx-drm display-subsystem: parent device of /soc/aips-bus at 02000000/ldb/lvds-channel at 1 is not available
> > [    2.875823] panel-simple panel: panel supply power not found, using dummy regulator
> > [    2.889177] imx-ipuv3 2400000.ipu: IPUv3H probed
> > [    2.896891] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> > [    2.903661] [drm] No driver support for vblank timestamp query.
> > [    2.910485] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops ipu_crtc_ops)
> > [    2.918297] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops ipu_crtc_ops)
> > [    2.926021] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops ipu_crtc_ops)
> > [    2.933794] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops ipu_crtc_ops)
> > [    2.942117] dwhdmi-imx 120000.hdmi: Detected HDMI TX controller v1.30a with HDCP (DWC HDMI 3D TX PHY)
> > [    2.953519] imx-drm display-subsystem: bound 120000.hdmi (ops dw_hdmi_imx_ops)
> > [    3.034254] imx-drm display-subsystem: fb0:  frame buffer device
> > [    3.042820] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0
> > [    3.050980] imx-ipuv3 2800000.ipu: IPUv3H probed
> > ...
> > [    4.344257] imx-pgc-pd imx-pgc-power-domain.1: Linked as a consumer to 20dc000.gpc
> > [    4.355939] etnaviv gpu-subsystem: bound 134000.gpu (ops gpu_ops)
> > [    4.362339] etnaviv gpu-subsystem: bound 130000.gpu (ops gpu_ops)
> > [    4.368696] etnaviv gpu-subsystem: bound 2204000.gpu (ops gpu_ops)
> > [    4.374910] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
> > [    4.448702] etnaviv-gpu 130000.gpu: model: GC2000, revision: 5108
> > [    4.513135] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
> > [    4.519437] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
> > [    4.531932] [drm] Initialized etnaviv 1.1.0 20151214 for gpu-subsystem on minor 1
> > 
> > Shawn
> 
> 
> Indeed I have the reverse order:
> 
> [    2.161526] etnaviv gpu-subsystem: bound 134000.gpu (ops gpu_ops)
> [    2.168071] etnaviv gpu-subsystem: bound 130000.gpu (ops gpu_ops)
> [    2.174409] etnaviv gpu-subsystem: bound 2204000.gpu (ops gpu_ops)
> [    2.180688] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
> [    2.236396] etnaviv-gpu 130000.gpu: model: GC2000, revision: 5108
> [    2.295886] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
> [    2.302070] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
> [    2.310488] [drm] Initialized etnaviv 1.1.0 20151214 for gpu-subsystem on minor 0
> [    2.321269] imx-ipuv3 2400000.ipu: IPUv3H probed
> [    2.328152] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [    2.334812] [drm] No driver support for vblank timestamp query.
> [    2.341592] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops ipu_crtc_ops)
> [    2.349325] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops ipu_crtc_ops)
> [    2.356998] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops ipu_crtc_ops)
> [    2.364703] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops ipu_crtc_ops)
> [    2.373190] imx-drm display-subsystem: bound 2000000.aips-bus:ldb (ops imx_ldb_ops)
> [    2.457551] Console: switching to colour frame buffer device 128x37
> [    2.483608] imx-drm display-subsystem: fb0:  frame buffer device
> [    2.492018] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1
> 
> 
> I *think* the reason is that I am using LVDS rather HDMI like you and the devices are declared in imx6qdl.dtsi in this order:
> 
> - hdmi
> - gpu
> - ldb

The DRM card nodes can change their numbering for many reasons, like DT
node ordering, device probe ordering, module vs. built-in configs, etc.
So please don't base any assumptions on the device number.

Regards,
Lucas