Hi,
On Mon, Jun 13, 2016 at 3:40 PM, Maxime Ripard
<[email protected]> wrote:
> On Thu, Jun 09, 2016 at 10:34:40AM +0200, Hans de Goede wrote:
>> Hi,
>>
>> On 09-06-16 09:53, Maxime Ripard wrote:
>> >Hi Hans,
>> >
>> >On Sat, Jun 04, 2016 at 08:10:54PM +0200, Hans de Goede wrote:
>> >>Hi All,
>> >>
>> >>As part of testing that my "ARM: dts: sun5i: Move display blocks to
>> >>sun5i.dtsi"
>> >>patch did not break anything I've been trying to get the sun4i-drm kms
>> >>driver to work on a q8 a13 tablet.
>> >>
>> >>I've build the drm / panel bits as modules after doing :
>> >>
>> >>[root@localhost ~]# insmod syscopyarea.ko
>> >>[root@localhost ~]# insmod sysfillrect.ko
>> >>[root@localhost ~]# insmod sysimgblt.ko
>> >>[root@localhost ~]# insmod fb_sys_fops.ko
>> >>[root@localhost ~]# insmod drm.ko
>> >>[root@localhost ~]# insmod drm_kms_helper.ko
>> >>[root@localhost ~]# insmod sun4i-tcon.ko
>> >>[root@localhost ~]# insmod sun4i_backend.ko
>> >>[root@localhost ~]# insmod panel-simple.ko
>> >>[root@localhost ~]# insmod sun4i-drm.ko
>> >>
>> >>I get the following in dmesg:
>> >>
>> >>[ 87.791338] [drm] Initialized drm 1.1.0 20060810
>> >>[ 113.883947] panel supply power not found, using dummy regulator
>> >>[ 119.199189] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>> >>[ 119.210695] [drm] No driver support for vblank timestamp query.
>> >>[ 119.238295] sun4i-drm display-engine: bound 1e60000.display-backend
>> >>(ops __mod_of__sun4i_backend_of_table_device_table [sun4i_backend])
>> >>[ 119.261666] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops
>> >>__mod_of__sun4i_tcon_of_table_device_table [sun4i_tcon])
>> >>[ 119.287566] checking generic (5fe89000 177000) vs hw (0 ffffffff)
>> >>[ 119.287599] fb: switching to sun4i-drm-fb from simple
>> >>[ 119.304752] Console: switching to colour dummy device 80x30
>> >>[ 119.319700] sun4i-drm display-engine: No connectors reported connected
>> >>with modes
>> >>[ 119.343392] [drm] Cannot find any crtc or sizes - going 1024x768
>> >>[ 119.374591] Console: switching to colour frame buffer device 128x48
>> >>[ 119.433258] sun4i-drm display-engine: fb0: frame buffer device
>> >>
>> >>Esp. notice the "sun4i-drm display-engine: No connectors reported
>> >>connected with modes"
>> >>and "[drm] Cannot find any crtc or sizes - going 1024x768"
>> >>
>> >>Which clearly is wrong, after this the lcd-panel display becomes
>> >>a mess, as if it is not getting any video data, which indeed
>> >>seems to be what is happening.
>> >
>> >Which panel is it using? Have you added the panel timings to the
>> >simple-panel driver?
>>
>> This is using the dts patches from Chen-Yu which you've recent merged into
>> next.
>
> Could you set drm.debug=0xff in the kernel command line, and paste the
> dmesg output?
I tried that, but it didn't give any more information.
On the side, I got some warnings about axp IRQs:
[ 1.169696] axp20x-i2c 0-0034: AXP20x variant AXP209 found
[ 1.192074] input: axp20x-pek as
/devices/platform/soc@01c00000/1c2ac00.i2c/i2c-0/0-0034/axp20x-pek/input/input1
[ 1.782501] random: nonblocking pool is initialized
[ 80.327487] irq 63: nobody cared (try booting with the "irqpoll" option)
[ 80.337724] CPU: 0 PID: 77 Comm: irq/63-axp20x_i Not tainted
4.7.0-rc4-00110-g4eb35c76ed74-dirty #34
[ 80.353741] Hardware name: Allwinner sun4i/sun5i Families
[ 80.362723] [<c010bc3d>] (unwind_backtrace) from [<c010937b>]
(show_stack+0xb/0xc)
[ 80.373969] [<c010937b>] (show_stack) from [<c02a140f>]
(dump_stack+0x6f/0x7c)
[ 80.384887] [<c02a140f>] (dump_stack) from [<c0154071>]
(__report_bad_irq+0x1d/0x8c)
[ 80.396336] [<c0154071>] (__report_bad_irq) from [<c0154347>]
(note_interrupt+0x1d7/0x214)
[ 80.408405] [<c0154347>] (note_interrupt) from [<c0152699>]
(handle_irq_event_percpu+0x79/0xc8)
[ 80.420959] [<c0152699>] (handle_irq_event_percpu) from
[<c015270f>] (handle_irq_event+0x27/0x3c)
[ 80.433840] [<c015270f>] (handle_irq_event) from [<c0154885>]
(handle_fasteoi_irq+0x71/0xf4)
[ 80.446381] [<c0154885>] (handle_fasteoi_irq) from [<c0151f93>]
(generic_handle_irq+0x17/0x20)
[ 80.459202] [<c0151f93>] (generic_handle_irq) from [<c0152197>]
(__handle_domain_irq+0x3b/0x7c)
[ 80.472202] [<c0152197>] (__handle_domain_irq) from [<c010134b>]
(sun4i_handle_irq+0x2f/0x3c)
[ 80.485171] [<c010134b>] (sun4i_handle_irq) from [<c0109c0d>]
(__irq_svc+0x4d/0x74)
[ 80.497280] Exception stack(0xdf747e98 to 0xdf747ee0)
[ 80.506776] 7e80:
df6f2360 df60ac00
[ 80.519489] 7ea0: 00000000 df747ee8 df6f2300 df6f2360 df700300
df6f2310 df700300 c0153109
[ 80.532221] 7ec0: c01532be 00000000 00000000 df747ee8 c05a4723
c05a4726 00000033 ffffffff
[ 80.544996] [<c0109c0d>] (__irq_svc) from [<c05a4726>]
(_raw_spin_unlock_irq+0xa/0x1c)
[ 80.557638] [<c05a4726>] (_raw_spin_unlock_irq) from [<c0153079>]
(irq_finalize_oneshot.part.1+0x41/0x80)
[ 80.576873] [<c0153079>] (irq_finalize_oneshot.part.1) from
[<c0153135>] (irq_thread_fn+0x2d/0x30)
[ 80.595664] [<c0153135>] (irq_thread_fn) from [<c0153349>]
(irq_thread+0x109/0x198)
[ 80.608310] [<c0153349>] (irq_thread) from [<c0132d41>] (kthread+0xa5/0xbc)
[ 80.620267] [<c0132d41>] (kthread) from [<c0105f71>]
(ret_from_fork+0x11/0x20)
[ 80.632419] handlers:
[ 80.639429] [<c0152755>] irq_default_primary_handler threaded
[<c0336049>] regmap_irq_thread
[ 80.652870] Disabling IRQ #63
Notice that it hangs for a bit after the AXP209 driver is loaded.
Also some warnings about musb:
[ 82.192238] BUG: sleeping function called from invalid context at
kernel/locking/mutex.c:97
[ 82.211008] in_atomic(): 1, irqs_disabled(): 128, pid: 81, name: kworker/0:2
[ 82.223346] CPU: 0 PID: 81 Comm: kworker/0:2 Not tainted
4.7.0-rc4-00110-g4eb35c76ed74-dirty #34
[ 82.237470] Hardware name: Allwinner sun4i/sun5i Families
[ 82.248198] Workqueue: events musb_deassert_reset
[ 82.258229] [<c010bc3d>] (unwind_backtrace) from [<c010937b>]
(show_stack+0xb/0xc)
[ 82.271152] [<c010937b>] (show_stack) from [<c02a140f>]
(dump_stack+0x6f/0x7c)
[ 82.283700] [<c02a140f>] (dump_stack) from [<c05a3009>]
(mutex_lock+0x15/0x2c)
[ 82.296204] [<c05a3009>] (mutex_lock) from [<c02bd7ad>]
(sun4i_usb_phy_write+0x35/0xd4)
[ 82.309521] [<c02bd7ad>] (sun4i_usb_phy_write) from [<c03beced>]
(musb_port_reset+0x41/0x14c)
[ 82.323446] [<c03beced>] (musb_port_reset) from [<c03bd73f>]
(musb_deassert_reset+0x1f/0x2c)
[ 82.337309] [<c03bd73f>] (musb_deassert_reset) from [<c012edf3>]
(process_one_work+0xc7/0x2b8)
[ 82.351370] [<c012edf3>] (process_one_work) from [<c012f0d7>]
(worker_thread+0xf3/0x418)
[ 82.364979] [<c012f0d7>] (worker_thread) from [<c0132d41>]
(kthread+0xa5/0xbc)
[ 82.377729] [<c0132d41>] (kthread) from [<c0105f71>]
(ret_from_fork+0x11/0x20)
I'm running the latest sunxi-next. Unfortunately my Q8 A13 tablet's UART RX pin
is broken, so I cannot debug the issue.
Regards
ChenYu
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
