Playing with upstream (Exynos4412)

Share here your ideas for new projects
User avatar
Panzerknacker
Posts: 248
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Fri Jan 18, 2019 5:47 pm

Had to disable DVFS again. Gives spurious hangs with heavy eMMC access.

User avatar
Panzerknacker
Posts: 248
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Thu Jan 24, 2019 11:16 pm

The reboot issue with eMMC has been fixed.
https://patchwork.kernel.org/patch/10778831/
Devfreq still needs to be disabled.

tve
Posts: 47
Joined: Sun Jul 13, 2014 4:02 pm
languages_spoken: english
ODROIDs: odroid-u3, odroid-c1, odroid-c1+
Has thanked: 0
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by tve » Fri Jan 25, 2019 1:18 am

Great spotting! Thanks for reporting. Are both patches necessary or only this last one?

User avatar
Panzerknacker
Posts: 248
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Sat Jan 26, 2019 12:19 am

The reboot issue with devfreq is resolved now in mainline, too.
https://patchwork.kernel.org/patch/10781431/

LiquidAcid
Posts: 1093
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Sat Jan 26, 2019 5:57 am

Panzerknacker wrote:
Sat Jan 26, 2019 12:19 am
The reboot issue with devfreq is resolved now in mainline, too.
https://patchwork.kernel.org/patch/10781431/
Good job triaging this!

User avatar
Panzerknacker
Posts: 248
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Fri Feb 01, 2019 7:05 pm

Just as a notice to save people's time.
During my experiments exploring the reboot issues I discovered that both my X2s do not reboot but hang, if the supply voltage is greater than 5,1 V.
The type of my boards is ODROID-X2+ Rev 0.5 20130228.
An older ODROID-X was not affected.

tve
Posts: 47
Joined: Sun Jul 13, 2014 4:02 pm
languages_spoken: english
ODROIDs: odroid-u3, odroid-c1, odroid-c1+
Has thanked: 0
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by tve » Sat Feb 02, 2019 2:07 am

Yikes, that's an odd one!

lucabelluccini
Posts: 21
Joined: Mon Feb 25, 2013 8:03 am
languages_spoken: english
ODROIDs: X
Has thanked: 0
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by lucabelluccini » Sun Mar 24, 2019 2:15 am

Hello all,
I would like to ask for some pointers to proceed further to make HDMI work on a Odroid-X.

I am trying Linux Arch Alarm ([link](https://archlinuxarm.org/platforms/armv ... g/odroid-x)).

USB, LAN, eMMC, SD card are working properly on Kernel 5.0.2.

I cannot manage HDMI work (I'm not asking even for hw acceleration, but just make it work for the console).
I can access both via SSH and Serial.

Just for a sanity check, I've tried a Debian distro to verify HDMI works and I can confirm it works properly.

I tried to pass the parameter "video=HDMI-A-1:1280x720M@60", but I get:

Code: Select all

[Sat Mar 23 16:13:07 2019] exynos-drm exynos-drm: bound 12d00000.hdmi (ops hdmi_component_ops [exynosdrm])
[Sat Mar 23 16:13:08 2019] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[Sat Mar 23 16:13:08 2019] [drm] No driver support for vblank timestamp query.
[Sat Mar 23 16:13:08 2019] s5p-mfc 13400000.codec: decoder registered as /dev/video2
[Sat Mar 23 16:13:08 2019] s5p-mfc 13400000.codec: encoder registered as /dev/video3
[Sat Mar 23 16:13:08 2019] [drm:hdmiphy_enable.part.1 [exynosdrm]] *ERROR* failed to find hdmiphy conf
[Sat Mar 23 16:13:08 2019] smsc95xx v1.0.6
[Sat Mar 23 16:13:08 2019] ------------[ cut here ]------------
[Sat Mar 23 16:13:08 2019] WARNING: CPU: 3 PID: 276 at drivers/gpu/drm/drm_atomic_helper.c:1424 drm_atomic_helper_wait_for_vblanks.part.1+0x28c/0x294
[Sat Mar 23 16:13:08 2019] [CRTC:44:crtc-0] vblank wait timed out
[Sat Mar 23 16:13:08 2019] Modules linked in: rfkill smsc95xx(+) usbnet mii s5p_mfc exynosdrm(+) analogix_dp exynos_adc s5p_jpeg v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common exynos_rng s5p_sss s3c2410_wdt s5p_cec evdev uio_pdrv_genirq uio sch_fq_codel ip_tables x_tables
[Sat Mar 23 16:13:08 2019] CPU: 3 PID: 276 Comm: kworker/3:3 Not tainted 5.0.2-1-ARCH #1
[Sat Mar 23 16:13:08 2019] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[Sat Mar 23 16:13:08 2019] Workqueue: events output_poll_execute
[Sat Mar 23 16:13:08 2019] [<c03111c8>] (unwind_backtrace) from [<c030bf10>] (show_stack+0x10/0x14)
[Sat Mar 23 16:13:08 2019] [<c030bf10>] (show_stack) from [<c0ee3a38>] (dump_stack+0x7c/0x90)
[Sat Mar 23 16:13:08 2019] [<c0ee3a38>] (dump_stack) from [<c03460c8>] (__warn+0xd4/0xf0)
[Sat Mar 23 16:13:08 2019] [<c03460c8>] (__warn) from [<c0345c8c>] (warn_slowpath_fmt+0x48/0x6c)
[Sat Mar 23 16:13:08 2019] [<c0345c8c>] (warn_slowpath_fmt) from [<c09a82a4>] (drm_atomic_helper_wait_for_vblanks.part.1+0x28c/0x294)
[Sat Mar 23 16:13:08 2019] [<c09a82a4>] (drm_atomic_helper_wait_for_vblanks.part.1) from [<c09a9f24>] (drm_atomic_helper_commit_tail_rpm+0x5c/0x6c)
[Sat Mar 23 16:13:08 2019] [<c09a9f24>] (drm_atomic_helper_commit_tail_rpm) from [<c09a9d6c>] (commit_tail+0x40/0x6c)
[Sat Mar 23 16:13:08 2019] [<c09a9d6c>] (commit_tail) from [<c09a9e5c>] (drm_atomic_helper_commit+0xbc/0x128)
[Sat Mar 23 16:13:08 2019] [<c09a9e5c>] (drm_atomic_helper_commit) from [<c09acca0>] (restore_fbdev_mode_atomic+0x1c4/0x1d4)
[Sat Mar 23 16:13:08 2019] [<c09acca0>] (restore_fbdev_mode_atomic) from [<c09b0638>] (drm_fb_helper_restore_fbdev_mode_unlocked+0x54/0xa4)
[Sat Mar 23 16:13:08 2019] [<c09b0638>] (drm_fb_helper_restore_fbdev_mode_unlocked) from [<c09b06b8>] (drm_fb_helper_set_par+0x30/0x54)
[Sat Mar 23 16:13:08 2019] [<c09b06b8>] (drm_fb_helper_set_par) from [<c09b05a0>] (drm_fb_helper_hotplug_event.part.11+0x90/0xa8)
[Sat Mar 23 16:13:08 2019] [<c09b05a0>] (drm_fb_helper_hotplug_event.part.11) from [<c09a0184>] (drm_kms_helper_hotplug_event+0x24/0x30)
[Sat Mar 23 16:13:08 2019] [<c09a0184>] (drm_kms_helper_hotplug_event) from [<c09a0348>] (output_poll_execute+0x18c/0x1ac)
[Sat Mar 23 16:13:08 2019] [<c09a0348>] (output_poll_execute) from [<c035e4b4>] (process_one_work+0x1f0/0x408)
[Sat Mar 23 16:13:08 2019] [<c035e4b4>] (process_one_work) from [<c035f33c>] (worker_thread+0x44/0x580)
[Sat Mar 23 16:13:08 2019] [<c035f33c>] (worker_thread) from [<c0364404>] (kthread+0x148/0x150)
[Sat Mar 23 16:13:08 2019] [<c0364404>] (kthread) from [<c03010e8>] (ret_from_fork+0x14/0x2c)
[Sat Mar 23 16:13:08 2019] Exception stack(0xed60bfb0 to 0xed60bff8)
[Sat Mar 23 16:13:08 2019] bfa0:                                     00000000 00000000 00000000 00000000
[Sat Mar 23 16:13:08 2019] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[Sat Mar 23 16:13:08 2019] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000
[Sat Mar 23 16:13:08 2019] ---[ end trace e4da785b211ced60 ]---
I am trying to understand if it's something being worked on (Exynos Mainline) or not working at all.

You'll find in attachment the dmesg.

Code: Select all

[Sat Mar 23 16:13:08 2019] [drm:hdmiphy_enable.part.1 [exynosdrm]] *ERROR* failed to find hdmiphy conf <
[Sat Mar 23 16:13:08 2019] [drm] No driver support for vblank timestamp query. <
[Sat Mar 23 16:13:08 2019] [CRTC:44:crtc-0] vblank wait timed out <
[    7.928656] OF: graph: no port node found in /soc/hdmi@12d00000 <
Attachments
output.drmparam.txt
(60.59 KiB) Downloaded 104 times

tve
Posts: 47
Joined: Sun Jul 13, 2014 4:02 pm
languages_spoken: english
ODROIDs: odroid-u3, odroid-c1, odroid-c1+
Has thanked: 0
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by tve » Tue Mar 26, 2019 2:21 pm

Panzerknacker wrote:
Sat Jan 26, 2019 12:19 am
The reboot issue with devfreq is resolved now in mainline, too.
https://patchwork.kernel.org/patch/10781431/
@Panzerknacker, dumb question, I'm not seeing the patch in linux-4.20.y, where is it expected to show up "in mainline"?

User avatar
Panzerknacker
Posts: 248
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Tue Mar 26, 2019 5:12 pm

Has been replaced by
https://patchwork.kernel.org/patch/10863169/
May land in 5.2?

tve
Posts: 47
Joined: Sun Jul 13, 2014 4:02 pm
languages_spoken: english
ODROIDs: odroid-u3, odroid-c1, odroid-c1+
Has thanked: 0
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by tve » Thu Mar 28, 2019 6:06 am

Ugh, at this rate it's going to maybe make it into Linux 7.x? ...

Anyway, I gave your odroid-4.20.y repo branch a shot on my U3 and reboot is still not working. Here's what happens:

Code: Select all

```
[  OK  ] Reached target Shutdown.
[  OK  ] Reached target Final Step.
         Starting Reboot...
[  649.737186] watchdog: watchdog0: watchdog did not stop!
[  650.391717] reboot: Restarting system
[  650.392573] Unable to handle kernel NULL pointer dereference at virtual address 00000049
[  650.398236] pgd = 2ac96e91
[  650.400807] [00000049] *pgd=00000000
[  650.404385] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[  650.409662] Modules linked in: xt_limit xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_physdev br_netfilter xt_mark xt
_helper iptable_raw xt_multiport nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_netlink nfnetlink aes_
arm_bs crypto_simd cryptd s5p_csis s5p_fimc exynos4_is_common v4l2_fwnode rt2800usb rt2800lib rt2x00usb rt2x00lib s5p_jpeg v
4l2_mem2mem s5p_mfc v4l2_common videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media s5p_cec
 bridge stp llc sch_fq_codel
[  650.455547] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 4.20.10-tve-g85a7d8e #1
[  650.462964] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[  650.469059] PC is at regulator_force_disable+0x8/0x160
[  650.474160] LR is at syscon_restart_handle+0x18/0x64
[  650.479095] pc : [<c051ffa4>]    lr : [<c0728f50>]    psr: a00f00d3
[  650.485351] sp : ee8e3de8  ip : cfeee050  fp : fffff000
[  650.490554] r10: 00000058  r9 : 00000000  r8 : cfee24b8
[  650.495762] r7 : 00000000  r6 : 00000000  r5 : 00000000  r4 : cfeee050
[  650.502280] r3 : c0728f38  r2 : 00000000  r1 : 00000000  r0 : ffffffed
[  650.508793] Flags: NzCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment none
[  650.516085] Control: 10c5387d  Table: 6c93004a  DAC: 00000051
[  650.521804] Process systemd-shutdow (pid: 1, stack limit = 0x3d71206a)
[  650.528320] Stack: (0xee8e3de8 to 0xee8e4000)
[  650.532655] 3de0:                   cfeee050 00000000 00000000 00000000 cfee24b8 00000000
[  650.540839] 3e00: 00000058 c0728f50 fffffffe 00000000 00000000 c0150530 c11bdd4a c111bc50
[  650.548994] 3e20: 00000000 00000000 ffffffff c01507b4 00000000 00000000 c0150734 c1110cb0
[  650.557154] 3e40: 000f423c 00000000 00000000 01234567 c111bc50 2da73700 fee1dead c015087c
[  650.565313] 3e60: 00000000 c111bc50 2da73700 c010c3cc c1110c88 00000000 01234567 c0152048
[  650.573472] 3e80: 00000000 00000000 00000000 00000000 ffffe000 00000000 600b0053 c1110cb0
[  650.581632] 3ea0: ee8e3f70 c018c258 c11113f0 c11bdec5 c11bfcf0 c01aa268 00000000 c02a701c
[  650.589790] 3ec0: 00000000 00000000 c1110c88 edabc140 00000024 ee8e3ef4 ee8e3f70 00000000
[  650.597950] 3ee0: be8830ec c02bf550 ee8e3ef0 ee8e3ef4 00000000 00000001 00000000 00000024
[  650.606108] 3f00: ee8e3f0c 00000005 ee8f048c be8830b0 00000004 be883ee9 00000010 be8830c4
[  650.614268] 3f20: 00000005 be88317c 0000000a b6e54b10 00000001 fffffe30 5ac3c35a c02a6808
[  650.622427] 3f40: c1110c88 fffffffe fffffffe e237d27d c1110c88 edabc140 edabc140 00000000
[  650.630586] 3f60: 00000000 c02bf5e8 00000000 c011611c 00000000 00000000 00000004 e237d27d
[  650.638746] 3f80: 00000001 e237d27d be88317c 004453ac 00000000 fffffffe 00000058 c01011c4
[  650.646907] 3fa0: ee8e2000 c0101000 004453ac 00000000 fee1dead 28121969 01234567 2da73700
[  650.655065] 3fc0: 004453ac 00000000 fffffffe 00000058 fffff000 00457590 00000000 fffff000
[  650.663224] 3fe0: 00000058 be8839cc b6f6ae35 b6eee206 600b0070 fee1dead 00000000 00000000
[  650.671396] [<c051ffa4>] (regulator_force_disable) from [<c0728f50>] (syscon_restart_handle+0x18/0x64)
[  650.680695] [<c0728f50>] (syscon_restart_handle) from [<c0150530>] (notifier_call_chain+0x44/0x84)
[  650.689619] [<c0150530>] (notifier_call_chain) from [<c01507b4>] (__atomic_notifier_call_chain+0x80/0x130)
[  650.699256] [<c01507b4>] (__atomic_notifier_call_chain) from [<c015087c>] (atomic_notifier_call_chain+0x18/0x20)
[  650.709418] [<c015087c>] (atomic_notifier_call_chain) from [<c010c3cc>] (machine_restart+0x7c/0x80)
[  650.718439] [<c010c3cc>] (machine_restart) from [<c0152048>] (sys_reboot+0x10c/0x1f8)
[  650.726243] [<c0152048>] (sys_reboot) from [<c0101000>] (ret_fast_syscall+0x0/0x28)
[  650.733872] Exception stack(0xee8e3fa8 to 0xee8e3ff0)
[  650.738893] 3fa0:                   004453ac 00000000 fee1dead 28121969 01234567 2da73700
[  650.747073] 3fc0: 004453ac 00000000 fffffffe 00000058 fffff000 00457590 00000000 fffff000
[  650.755229] 3fe0: 00000058 be8839cc b6f6ae35 b6eee206
[  650.760249] Code: e5840008 e8bd8010 e92d47f0 e3a01000 (e590405c)
[  650.766332] ---[ end trace daf880ce50191fdc ]---
[  650.782343] watchdog: watchdog0: watchdog did not stop!
[  650.782562] printk: systemd-shutdow: 4 output lines suppressed due to ratelimiting
[  650.790044] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[  650.797214] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
```

LiquidAcid
Posts: 1093
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Sat Mar 30, 2019 3:27 am

Looks like you're not using the correct DT, otherwise it should find the regulator.

LiquidAcid
Posts: 1093
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Sat May 11, 2019 5:28 pm

FYI, just pushed odroid-5.1.y, based on vanilla-5.1.1.
These users thanked the author LiquidAcid for the post:
Panzerknacker (Sat May 11, 2019 5:44 pm)

henriku
Posts: 12
Joined: Tue May 05, 2015 6:32 am
languages_spoken: english
ODROIDs: U3
Has thanked: 0
Been thanked: 0
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by henriku » Sun May 19, 2019 12:34 am

The lima driver which supports Mali-400 has been merged in mainline and should land in linux 5.2. Has anyone tested this with Exynos 4412?

https://github.com/torvalds/linux/commi ... e9e9a8e119

Post Reply

Return to “The Ideas”

Who is online

Users browsing this forum: No registered users and 2 guests