Message-ID: <b80923e8e32e9605c150a5de761db88a@agner.ch>
Date:	Tue, 24 May 2016 23:20:02 -0700
From:	Stefan Agner <stefan@...er.ch>
To:	Meng Yi <meng.yi@....com>
Cc:	dri-devel@...ts.freedesktop.org, David Airlie <airlied@...ux.ie>,
	airlied@...hat.com, linux-kernel@...r.kernel.org,
	Mark Brown <broonie@...nel.org>,
	alexander.stein@...tec-electronic.com
Subject: RE: fsl-dcu not works on latest "drm-next"

On 2016-05-24 19:14, Meng Yi wrote:
> I found that its regmap endianness issue, so I want to replace the "regmap".
Hm, replace with what? Note that we need some kind of endianness
convertion since the IP is big endian on LS1021a and little endian on
Vybrid (vf610).

Is it maybe just an issue with regmap/the big-endian property in the
device tree? Maybe this thread is interesting for you:
https://lkml.org/lkml/2016/3/23/233

[adding Alexander Stein, he might be able to tell more about this issue]

--
Stefan

> 
> Hi Stefan,
> Do you have any idea about this?
> 
> Hi Mark,
> Regmap endianness issue had caused some other drivers not work, like SPI etc. 
> Or this is fixed and I just don't know?
> 
> Thanks,
> Meng
> 
> ---------------------------------------------------------------------
> From: Meng Yi 
> Sent: Tuesday, May 03, 2016 5:27 PM
> To: 'dri-devel@...ts.freedesktop.org'
> <dri-devel@...ts.freedesktop.org>; David Airlie <airlied@...ux.ie>;
> 'Stefan Agner' <stefan@...er.ch>; 'airlied@...hat.com'
> <airlied@...hat.com>
> Subject: fsl-dcu not works on latest "drm-next"
> 
> Hi,
> 
> 
> I just tested the latest drm-next branch on Freescale/NXP ls1021a-twr,
> and got some log below. And fsl-dcu not works.
> 
> Since "drm-next" merged some branch , use git bisect had some problem ,
> 
> so I manually checked out that "fsl-dcu" works at
> d761701c55a99598477f3cb25c03d939a7711e74
> 
> And not works now. some log below:
> 
> --------------------------------------------------------------------
> 
> [drm] Initialized drm 1.1.0 20060810
> panel supply power not found, using dummy regulator
> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [drm] No driver support for vblank timestamp query.
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/drm_atomic_helper.c:1106
> drm_atomic_helper_wait_for_vblanks+0xff/0x124
> [CRTC:24] vblank wait timed out
> Modules linked in:
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.6.0-rc3+ #189
> Hardware name: Freescale LS1021A
> [<80209a7b>] (unwind_backtrace) from [<8020755f>] (show_stack+0xb/0xc)
> [<8020755f>] (show_stack) from [<803676a3>] (dump_stack+0x5b/0x74)
> [<803676a3>] (dump_stack) from [<80211a37>] (__warn+0x87/0xb0)
> [<80211a37>] (__warn) from [<80211a7f>] (warn_slowpath_fmt+0x1f/0x28)
> [<80211a7f>] (warn_slowpath_fmt) from [<803ca887>]
> (drm_atomic_helper_wait_for_vblanks+0xff/0x124)
> [<803ca887>] (drm_atomic_helper_wait_for_vblanks) from [<803cb307>]
> (drm_atomic_helper_commit+0x43/0x5c)
> [<803cb307>] (drm_atomic_helper_commit) from [<803cbe51>]
> (restore_fbdev_mode+0xad/0x16e)
> [<803cbe51>] (restore_fbdev_mode) from [<803ccf4d>]
> (drm_fb_helper_restore_fbdev_mode_unlocked+0x19/0x44)
> [<803ccf4d>] (drm_fb_helper_restore_fbdev_mode_unlocked) from
> [<803ccf9d>] (drm_fb_helper_set_par+0x25/0x38)
> [<803ccf9d>] (drm_fb_helper_set_par) from [<80397451>] (fbcon_init+0x1fd/0x2c0)
> [<80397451>] (fbcon_init) from [<803b6051>] (visual_init+0x71/0xb4)
> [<803b6051>] (visual_init) from [<803b6f95>] (do_bind_con_driver+0x105/0x1e4)
> [<803b6f95>] (do_bind_con_driver) from [<803b7287>]
> (do_take_over_console+0xcf/0x108)
> [<803b7287>] (do_take_over_console) from [<80397549>]
> (do_fbcon_takeover+0x35/0x7c)
> [<80397549>] (do_fbcon_takeover) from [<802229db>]
> (notifier_call_chain+0x23/0x38)
> [<802229db>] (notifier_call_chain) from [<80222b63>]
> (__blocking_notifier_call_chain+0x27/0x36)
> [<80222b63>] (__blocking_notifier_call_chain) from [<80222b81>]
> (blocking_notifier_call_chain+0xf/0x14)
> [<80222b81>] (blocking_notifier_call_chain) from [<8039bdf9>]
> (register_framebuffer+0x179/0x1d0)
> [<8039bdf9>] (register_framebuffer) from [<803cd15f>]
> (drm_fb_helper_initial_config+0x1af/0x200)
> [<803cd15f>] (drm_fb_helper_initial_config) from [<803cd593>]
> (drm_fbdev_cma_init+0x67/0xa8)
> [<803cd593>] (drm_fbdev_cma_init) from [<803e2269>]
> (fsl_dcu_fbdev_init+0x11/0x14)
> [<803e2269>] (fsl_dcu_fbdev_init) from [<803e18eb>] (fsl_dcu_load+0x81/0xba)
> [<803e18eb>] (fsl_dcu_load) from [<803d2d51>] (drm_dev_register+0x3d/0x68)
> [<803d2d51>] (drm_dev_register) from [<803e1ab7>]
> (fsl_dcu_drm_probe+0x193/0x240)
> [<803e1ab7>] (fsl_dcu_drm_probe) from [<803e6d2d>]
> (platform_drv_probe+0x33/0x62)
> [<803e6d2d>] (platform_drv_probe) from [<803e5e7d>]
> (driver_probe_device+0xb9/0x1a4)
> [<803e5e7d>] (driver_probe_device) from [<803e5fad>] (__driver_attach+0x45/0x58)
> [<803e5fad>] (__driver_attach) from [<803e4eeb>] (bus_for_each_dev+0x3b/0x46)
> [<803e4eeb>] (bus_for_each_dev) from [<803e5897>] (bus_add_driver+0x7b/0x138)
> [<803e5897>] (bus_add_driver) from [<803e6469>] (driver_register+0x4b/0x76)
> [<803e6469>] (driver_register) from [<80201517>] (do_one_initcall+0xb3/0x138)
> [<80201517>] (do_one_initcall) from [<80800a61>]
> (kernel_init_freeable+0xd1/0x168)
> [<80800a61>] (kernel_init_freeable) from [<80558d13>] (kernel_init+0x7/0xb4)
> [<80558d13>] (kernel_init) from [<80205261>] (ret_from_fork+0x11/0x30)
> ---[ end trace b7946726c4e290c4 ]---
> Console: switching to colour frame buffer device 60x34
> fsl-dcu 2ce0000.dcu: fb0:  frame buffer device
> [drm] Initialized fsl-dcu-drm 1.1.0 20160425 on minor 0
> 
> 
> And full log in the attachment.
> 
> does anybody have any idea about this?
> 
> Best Regards,
> Meng Yi

Powered by blists - more mailing lists