eglinitialize depends on /dev/galcore and not available for sometime causing delay in weston boot

[arunkumar_rajag]

NXP BSP Version: is4.14.98_2.0.0_ga

U-Boot and kernel completes @ 3.7sec.

systemd started galcore module.

and in parallel weston started.

Weston takes 1.2sec to complete initialization.

But if we delay weston startup around 1sec in systemd then weston comepleted init in ~250ms.

find below strace.....

1344  18:22:33.206979 openat(AT_FDCWD, "/dev/galcore", O_RDWR) = -1 ENOENT (No such file or directory)

1344  18:22:33.207208 openat(AT_FDCWD, "/dev/graphics/galcore", O_RDWR) = -1 ENOENT (No such file or directory)

1344  18:22:33.207409 nanosleep({tv_sec=1, tv_nsec=0}, NULL) = 0

1344  18:22:34.212621 write(2, "[     1] Failed to open device: "..., 72) = 72

1344  18:22:34.212954 openat(AT_FDCWD, "/dev/galcore", O_RDWR) = 13

1344  18:22:34.214095 ioctl(13, _IOC(0, 0x75, 0x30, 0), 0xffffffca22e0) = 0

1344  18:22:34.215424 ioctl(13, _IOC(0, 0x75, 0x30, 0), 0xffffffca22e0) = 0

So why dev/galcore taking more time to be available?

Can we move this galcore module insertion to kernel? what is the NXP recommandation?

Why nanosleep configured to 1sec sleep? can we reduce it?

danweiluo‌

Thanks,

Arunkumar R

[IvanRuiz]

Hello,

May I ask which part number you are working with? -Because it was tagged many variants of the i.MX8 in the thread. Also, please confirm if it is an evaluation board or a custom one?

One more question, may I ask if you already have an FAE assigned or if you are already in touch with an internal NXP expert?

Thank you.

BR,

Ivan.

[arunkumar_rajag]

Hi Ivan,

We are working with imx8qx.

It is a custom board.

danweiluo and rao.mr@nxp.com 

Use to support us.

Thanks,

Arunkumar R

[danwei_luo · Accepted solution]

Hi Arunkumar Rajagopal，

.

Sure, you can build the galcore.ko into kernel as build-in. In the latest Linux BSP, it's set as build-in by default.

Best regards,

Danwei