09:58 <PabloPL> Is Exynos MFC working for anyone on mainline kernel (for example 4.20)? I'm getting very strange kernel oops after just enabling this module (since around 4.19.rc7 - i think it was working fine around rc4)

09:59 <PabloPL> Unable to handle kernel NULL pointer dereference at virtual address 00000000

09:59 <PabloPL> / stacktrace

09:59 <PabloPL> [ 8.992674] [<803d7e44>] (platform_match) from [<803d62f4>] (__device_attach_driver+0x38/0xcc)

09:59 <PabloPL> [ 8.975210] [<805b8f70>] (strcmp) from [<803d7e44>] (platform_match+0xa8/0xbc)

09:59 <PabloPL> [ 9.011590] [<803d62f4>] (__device_attach_driver) from [<803d4324>] (bus_for_each_drv+0x58/0xb8)

09:59 <PabloPL> [ 9.030683] [<803d4324>] (bus_for_each_drv) from [<803d5c40>] (__device_attach+0xd0/0x138)

09:59 <PabloPL> [ 9.049271] [<803d5c40>] (__device_attach) from [<803d5148>] (bus_probe_device+0x84/0x8c)

10:00 <PabloPL> [ 9.067794] [<803d5148>] (bus_probe_device) from [<803d20e0>] (device_add+0x41c/0x624)

10:00 <PabloPL> [ 9.086180] [<803d20e0>] (device_add) from [<7f1868b4>] (s5p_mfc_alloc_memdev+0x84/0xc8 [s5p_mfc])

10:00 <PabloPL> [ 9.105675] [<7f1868b4>] (s5p_mfc_alloc_memdev [s5p_mfc]) from [<7f186db8>] (s5p_mfc_probe+0x4bc/0x868 [s5p_mfc])

10:02 <PabloPL> If this errors shows, it also shows at the same time in brcmfmac (probed later), but if i disable MFC (when building), this issue is not happening and all is working fine

10:05 <mszyprow> PabloPL: seems to be working fine, at least built-in

10:05 <mszyprow> PabloPL: tested on v4.20 on trats2

10:06 <PabloPL> ok, will try to built-in it. didn't tried to bisect it yet

10:06 <mszyprow> PabloPL: this doesn't exclude the fact that it might fail if build as module

10:06 <mszyprow> PabloPL: let me check this

10:07 <PabloPL> mszyprow: strange that it was working, i was testing mfc (after adding missing reserved memory nodes for s5pv210). didn't tried to bisect it yet

10:12 <mszyprow> PabloPL: reproduced

10:13 <mszyprow> PabloPL: seems to be relatedto no-iommu support

10:14 <PabloPL> mszyprow: ok, i remember that it was working around 4.19.rc4 and broke at 4.19.rc7 (or even i lower version)

10:14 <PabloPL> mszyprow: should i try to bisect it?

10:15 <mszyprow> PabloPL: no need, I will check this in a few minutes

10:15 <PabloPL> mszprow: Great, thanks !

10:19 <PabloPL> mszyprow: btw was able to fix issues with mainline uboot and eMMC as mass storage on aries. https://github.com/xc-racer99/u-boot-galaxys4g/commit/7e751883b4adfe456e297a8121dbcf5a47b85c71

10:20 <PabloPL> mszyprow: Someone was saying that have similar issues on trats/trats2, maybe it would also "fix" it

10:21 <mszyprow> PabloPL: btw, if you still have issues with dwc2 (usb gadget), apply those patches: https://patchwork.kernel.org/patch/10690537/ https://patchwork.kernel.org/patch/10721319/

10:24 <PabloPL> mszyprow: don't i need to have/submit extcon driver first? there is one existing for fsa9480 (done by tom3q 4 years ago), working fine ;)

10:25 <mszyprow> extcon support is independent from udc driver

10:26 <mszyprow> having both is probably required for all features though

10:56 <mszyprow> PabloPL: commit a66d972465d15b1d89281258805eb8b47d66bd36 causes this null ptr issue, no idea why yet, but I need to go now. I will investigate it in 2019 once I get back to the office

10:57 <PabloPL> mszyprow: Ok, thanks!