Skip to content

Conversation

@faxe1008
Copy link
Contributor

@faxe1008 faxe1008 commented Aug 30, 2023

This is a follow up to the PR: pull/60867

The goal is basically to remove the depedency of lvgl on the kscan nodes. This means in any case the defconfigs where KSCAN and LV_Z_POINTER_KSCAN are enabled need to be edited.

I split the removal of the kscan nodes into a separate commit since I am not sure if the fact that this will break downstream applications breaks any sort of deprecation timeline. If its fine I can squash the commit 3 into the first one.

If having the pointer be a freestanding node is a concern, I'd be happy to change zephyr,lvgl-pointer-input to be similar to the way kscan-input worked prior. Feedback on this would also be appreciated :^)

@faxe1008 faxe1008 force-pushed the board_remove_kscan branch 2 times, most recently from b3fb3b8 to 6890a88 Compare August 30, 2023 12:22
@faxe1008 faxe1008 marked this pull request as ready for review August 30, 2023 14:10
@zephyrbot zephyrbot added area: Display area: native port Host native arch port (native_sim) area: Kscan area: Shields Shields (add-on boards) platform: Laird Connectivity Laird Connectivity platform: STM32 ST Micro STM32 platform: NXP NXP labels Aug 30, 2023
@fabiobaltieri fabiobaltieri requested review from fabiobaltieri and removed request for decsny August 31, 2023 09:05
fabiobaltieri
fabiobaltieri previously approved these changes Sep 4, 2023
Change boards and shields which enable the LV_Z_POINTER_KSCAN symbol to use
the new "zephyr,lvgl-pointer-input" compatible instead.

Signed-off-by: Fabian Blatz <[email protected]>
After adding the lvgl pointer device into the board dts the custom overlays
are not needed anymore.

Signed-off-by: Fabian Blatz <[email protected]>
Change boards and shields and remove kscan nodes in favor of the
"zephyr,lvgl-pointer-input" compatible.

Signed-off-by: Fabian Blatz <[email protected]>
Update the expected output of the init priority checking.

Signed-off-by: Fabian Blatz <[email protected]>
@faxe1008
Copy link
Contributor Author

faxe1008 commented Sep 4, 2023

Addressed @erwango note regarding naming of nodes within shields.
@fabiobaltieri Should I be squashing commit 3 into commit 1?

@fabiobaltieri
Copy link
Member

Should I be squashing commit 3 into commit 1?

Up to you, does it break the build to have that change in its own commit?

@faxe1008
Copy link
Contributor Author

faxe1008 commented Sep 4, 2023

Should I be squashing commit 3 into commit 1?

Up to you, does it break the build to have that change in its own commit?

Build should succeed regardless of the squashing. If you want to I'll squash, for me its fine as is :^).

@fabiobaltieri
Copy link
Member

Build should succeed regardless of the squashing. If you want to I'll squash, for me its fine as is :^).

Ok so fine as is.

Copy link
Member

@erwango erwango left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved (even if I can't see the proposed changed, so will have to be fixed in an upcoming PR)

@carlescufi carlescufi merged commit 594e919 into zephyrproject-rtos:main Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Display area: Kscan area: native port Host native arch port (native_sim) area: Shields Shields (add-on boards) platform: Laird Connectivity Laird Connectivity platform: NXP NXP platform: STM32 ST Micro STM32

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants