fix(stdlib): fix issues when using LVGL TLSF memory pool to manage more than 4 GiB of memory

[MouriNaruto]

Description of the feature or fix

People will know that I'm developing UEFI applications with LVGL in recent days after read #5391 (comment).

Because UEFI memory pool will cause many memory fragments. So, my project uses LVGL builtin TLSF memory pool to manage the memory. And I found if I use LVGL TLSF memory pool to manage more than 4 GiB of memory, I cannot get the correct result via lv_mem_monitor API.

I also found the original LVGL implementation have considered about the 64-bit environments and many lv_mem APIs use size_t to manage size. So, I think it should not break the ABI for 32-bit environments if we use size_t type instead of uint32_t type to fix the issue. (For 64-bit LVGL users needs to recompile. But I think most people don't use 64-bit LVGL instance in the current stage. It should be acceptable.)

Notes

• Update the Documentation if needed.
• Add Examples if relevant.
• Add Tests if applicable.
• If you added new options to lv_conf_template.h run lv_conf_internal_gen.py and update Kconfig.
• Run scripts/code-format.py (astyle version v3.4.10 needs to be installed) and follow the Code Conventions.
• Mark the Pull request as Draft while you are working on the first version, and mark is as Ready when it's ready for review.
• When changes were requested, re-request review to notify the maintainers.
• Help us to review this Pull Request! Anyone can approve or request changes.

Kenji Mouri

[MouriNaruto]

I think there are some issues should be also fixed for LVGL. (Need some time to do.)

Kenji Mouri

[MouriNaruto]

It looks like all CIs are passed. It should be continued.

Kenji Mouri

[MouriNaruto]

Here is the screenshot of just using LVGL TLSF memory pool with this fix to manage 6 GiB of memory in my test virtual machine.

Kenji Mouri

[kisvegabor]

Awesome, thank you!