draw: dma2d: add zephyr infrastructure to support #61
Conversation
uLipe
force-pushed
the
feature/dma2d_zephyr
branch
from
fa62cdc to
62b182a
Compare
|
It seems the CI errors are not related to this PR |
uLipe
force-pushed
the
feature/dma2d_zephyr
branch
from
62b182a to
125b2eb
Compare
acceleration of the DMA2D peripheral Signed-off-by: Felipe Neves <[email protected]>
uLipe
force-pushed
the
feature/dma2d_zephyr
branch
from
125b2eb to
3b84511
Compare
There was a problem hiding this comment.
Change it's self looks ok now. We have two possibilities:
- Change the destination of this PR to a temporary branch based on master. We can not merge this to master since with the next sync there will be merge conflicts otherwise
- Upstream this to LVGL master and get this in with the next sync
In any case would be lovely to have a PR (even if its only a draft) inside of the zephyr main repo to verify that this PR builds and also make testing easier. I myself do not own a board with that graphics engine but maybe @CharlesDias can take a look (he added the initial gluecode to zephyr)
|
@faxe1008 I like the second approach, I already tested it successfully on a H7 board that I have, so I can PR it to zephyr master branch as draft and source for testing Meanwhile I can move this change to the lvgl upstream, then after 9.3 release it can be synced and the draft PR of zephyr gets up to date. |
|
@faxe1008, I will closing this PR, since there is a better way to enable the DMA2D on Zephyr side without touching at least for now on LVGL files. Maybe this thing can be addresed on zephyr side only. |
2 participants
Add zephyr infrastructure to make the DMA2D to work on it, the idea takes inspiration on how PXP does that, the idea is to start from zephyr-lvgl side, and then eventually move it to the lvgl upstream.