[Freedreno] help: mipi dsi drm driver on 8084
vinay simha
vinaysimha at inforcecomputing.com
Mon Apr 20 03:21:05 PDT 2015
Now the dsi data path is working, the lanes got swapped and data0 and data1
is enabled in dsi_host.c. added the panel description in apq8084-mdss.dtsi,
attached the dsi encoder :)
Still the dsi data is not clear in the panel,flickering,data is not clear
debugging on it.
update the branch
https://github.com/vinaysimha/kernel-msm-ifc6410/commits/ifc6540-drm-4.4.4-dsi
modetest output
Encoders:
id crtc type possible crtcs possible clones
29 18 DSI 0x0000000f 0x00000000
30 0 DSI 0x0000000f 0x00000000
32 0 TMDS 0x0000000f 0x00000000
Connectors:
id encoder status type size (mm) modes encoders
31 29 connected DSI 0x0 1
29
modes:
name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
480x864 60 480 526 530 574 864 879 880 896 flags: ; type:
Regards,
vinay simha
On Wed, Apr 15, 2015 at 10:25 PM, <hali at codeaurora.org> wrote:
> > fyi,
> >
> > dmesg log for dsi
> > http://pastebin.com/nD68gNNM
> >
> > Regards,
> > vinay simha
> >
> > On Wed, Apr 15, 2015 at 8:04 PM, vinay simha <
> > vinaysimha at inforcecomputing.com> wrote:
> >
>
> Since the host can send commands to the panel, the connection should be
> OK. The next thing is to make sure the panel power on sequence and
> commands are correct.
> For the host side, since this is 2-lane panel, the host assumes the lane
> mappings. You can try to change value in REG_DSI_LANE_SWAP_CTRL and enable
> different DSI_CTRL_LANEx bit in REG_DSI_CTRL, if it does need to be
> different from panel to another, we may need to add this information to
> mipi dsi panel framework, or device tree.
>
> Thanks,
> Hai
>
> >> Hai,
> >>
> >> i tried both mipi_dsi_generic_write and mipi_dsi_dcs_write_buffer. It
> >> doesn't returns error but there is no change in the display panel. if we
> >> write 0x11, 0x29 and 0x23 to panel , all pixels should be on in dsi
> >> panel.
> >> but nothing happens.
> >>
> >> fyi, attached dmesg log
> >>
> >> I will check on the encoder.
> >>
> >> Regards,
> >> vinay simha
> >>
> >> On Wed, Apr 15, 2015 at 7:50 PM, <hali at codeaurora.org> wrote:
> >>
> >>> Hi Vinay,
> >>> > On Wed, Apr 15, 2015 at 9:22 AM, vinay simha
> >>> > <vinaysimha at inforcecomputing.com> wrote:
> >>> >> Hai,
> >>> >>
> >>> >> added the panel in dts, now the new panel-truly is getting probed.
> >>> >> updated
> >>> >> my branch
> >>> >>
> >>>
> https://github.com/vinaysimha/kernel-msm-ifc6410/commits/ifc6540-drm-4.4.4-dsi
> >>> >>
> >>> >> panel backlight is up, hdmi display is coming. No data in the dsi.
> >>> >> i had not used this function dsi_host_init_panel_gpios, since
> >>> gpiolib.c
> >>> >> is
> >>> >> different from 4.x kernel to 3.10.40 kernel. i handled the gpios in
> >>> >> panel-truly.c
> >>> >>
> >>> >> Does these reg address are correct ?
> >>> >>
> >>> >> mdss_dsi0: qcom,mdss_dsi at fd922800
> >>> >> reg = <0xfd922800 0x200>,
> >>> >> <0xfd922b00 0x20c>,
> >>> >> <0xfd922d80 0x20>,
> >>> >> <0xfd828000 0x108>;
> >>> >> reg-names = "dsi_ctrl", "dsi_phy", "dsi_phy_regulator",
> >>> >> "mmss_misc_phys";
> >>> >>
> >>> >> }
> >>> >>
> >>> >> When i tried the modetest,
> >>> >> hdmi encoders is set properly to 32 , crtc 20
> >>> >> But for the dsi encoder set to 1 is not correct i guess. It should
> >>> be
> >>> >> 29.
> >>> >
> >>> > fwiw, I tihnk "1" is number of modes, and there are no encoders..
> >>> >
> >>> > btw, that modetest output made me realize that modetest needed to be
> >>> > updated with new encoder/connector names.. I just pushed a fix so it
> >>> > won't show "invalid" for DSI connector/encoder types:
> >>> >
> >>> >
> >>>
> http://cgit.freedesktop.org/mesa/drm/commit/?id=0d78b37b1cac304ce5e84d1207f0a43abd29c000
> >>> >
> >>> > BR,
> >>> > -R
> >>> >
> >>> >
> >>> >> Any suggestions?
> >>> >>
> >>> >> -----------------------------------
> >>> >> Encoders:
> >>> >> id crtc type possible crtcs possible clones
> >>> >> 29 18 (invalid) 0x0000000f 0x00000000
> >>> >> 30 0 (invalid) 0x0000000f 0x00000000
> >>> >> 32 20 TMDS 0x0000000f 0x00000000
> >>> >>
> >>> >> ************************************************
> >>> >> Connectors:
> >>> >> id encoder status type size (mm) modes encoders
> >>> >> 31 29 connected (invalid) 0x0 1
> >>> >> ************************************************
> >>> >> modes:
> >>> >> name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
> >>> >> 480x864 60 480 526 530 574 864 879 880 896 flags: ; type:
> >>> >> props:
> >>> >> 1 EDID:
> >>> >> flags: immutable blob
> >>> >> blobs:
> >>> >>
> >>> >> value:
> >>> >> 2 DPMS:
> >>> >> flags: enum
> >>> >> enums: On=0 Standby=1 Suspend=2 Off=3
> >>> >> value: 0
> >>> >> ***********************************************
> >>> >> 33 32 connected HDMI-A 480x270 28 32
> >>> >> ***********************************************
> >>> >> modes:
> >>> >> name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
> >>> >> 1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 flags:
> >>> phsync,
> >>> >> pvsync; type: preferred, driver
> >>> >> 1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 flags:
> >>> phsync,
> >>> >> pvsync; type: driver
> >>> >>
> >>> >> CRTCs:
> >>> >> id fb pos size
> >>> >> 18 60 (0,0) (480x864)
> >>> >> 480x864 60 480 526 530 574 864 879 880 896 flags: ; type:
> >>> >> props:
> >>> >> 20 60 (0,0) (1920x1080)
> >>> >> 1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 flags:
> >>> phsync,
> >>> >> pvsync; type: preferred, driver
> >>> >> props:
> >>> >> -----------------------------------------------------
> >>> >>
> >>> >> Regards,
> >>> >> vinay simha
> >>> >>
> >>>
> >>> Is there error message during power on? Are the commands sent to the
> >>> panel
> >>> successfully?
> >>> Also, it is worth to check why modetest returns no encoder.
> >>>
> >>> Thanks,
> >>> Hai
> >>>
> >>>
> >>
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/freedreno/attachments/20150420/899cc8aa/attachment.html>
More information about the Freedreno
mailing list