Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Demo for the OSAL #6049

Open
faxe1008 opened this issue Apr 9, 2024 · 4 comments · May be fixed by #6182
Open

Demo for the OSAL #6049

faxe1008 opened this issue Apr 9, 2024 · 4 comments · May be fixed by #6182
Labels
pinned Not closed automatically stale

Comments

@faxe1008
Copy link
Contributor

faxe1008 commented Apr 9, 2024

Problem to solve

During development of LVGL integrations one task with the new release is the support of the OSAL. It would be very useful to have tests of some sort that integrators could refer to to verify their implementation.

Success criteria

LVGL integrators have a convenient way of verifying their OSAL implementation

Solution outline

I would propose this to be a demo rather then a feature though, because there might be customer preferences as to what framework to use. A demo could be vendor neutral way to provide the results by using print statements and LV_ASSERT etc.

Rabbit holes

None that I know of.

Testing

Running integrations tests (at least for a linux pthread osal) within the pipeline.

Teaching

Adding a note to the OS porting section and of course to the demos.

Considerations

No response

@kisvegabor
Copy link
Member

Hi,

Just to be sure I understand correctly: in a demo or example we should create a few mutexes and threads with printf-s to demonstrate that OS layer is working well.

If so, I think it should be rather an example which could be also a good starting point for anyone using LVGL with an OS. (E.g. show that lv_timer_handler needs to be protected by a mutex). I can imagine something like this:

  1. We have the main thread in which a button is create
  2. A new thread is created, which creates a label, and waits for a signal
  3. When the button is pressed, a signal is triggered, and the other thread increments a counter and updates the label.

Besides the example - as you have mentioned - there should be a test too at least for pthread, but I think it's simpler as we can write any complicated code.

@lvgl-bot
Copy link

We need some feedback on this issue.

Now we mark this as "stale" because there was no activity here for 14 days.

Remove the "stale" label or comment else this will be closed in 7 days.

@lvgl-bot lvgl-bot added the stale label Apr 30, 2024
@kisvegabor
Copy link
Member

Sorry for not responding. GitHub doesn't send notification about reactions and I didn't notice the 👍

We will work on it!

@kisvegabor kisvegabor added the pinned Not closed automatically label May 2, 2024
@faxe1008
Copy link
Contributor Author

faxe1008 commented May 2, 2024

Hey @kisvegabor 😃, no worries. Maybe I'll find some time to work on this :^)

faxe1008 added a commit to faxe1008/lvgl that referenced this issue May 5, 2024
Adds a demo demonstrating the use of the OSAL.

Resolves: lvgl#6049
@faxe1008 faxe1008 linked a pull request May 5, 2024 that will close this issue
faxe1008 added a commit to faxe1008/lvgl that referenced this issue May 16, 2024
Adds a demo demonstrating the use of the OSAL.

Resolves: lvgl#6049
faxe1008 added a commit to faxe1008/lvgl that referenced this issue May 16, 2024
Adds a example demonstrating the use of the OSAL.

Resolves: lvgl#6049
faxe1008 added a commit to faxe1008/lvgl that referenced this issue May 16, 2024
Adds a example demonstrating the use of the OSAL.

Resolves: lvgl#6049
faxe1008 added a commit to faxe1008/lvgl that referenced this issue May 22, 2024
Adds a example demonstrating the use of the OSAL.

Resolves: lvgl#6049
faxe1008 added a commit to faxe1008/lvgl that referenced this issue May 22, 2024
Adds a example demonstrating the use of the OSAL.

Resolves: lvgl#6049
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pinned Not closed automatically stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants