Skip to content

Conversation

decsny
Copy link
Member

@decsny decsny commented Oct 6, 2025

Handle the case where there are multiple different kinds of UART on one platform, the other UART driver select SERIAL_SUPPORT_ASYNC but LPUART did not, causing build error in LPUART driver. Shield LPUART driver from this case by introducing driver config to indicate that in fact LPUART is the one enabling ASYNC.

Fixing CI issue for example on #96983

Might fix #97022 , not sure @hakehuang ?

@decsny decsny added the Hotfix Fix for issues blocking development, i.e. CI issues, tests failing in CI, etc. label Oct 6, 2025
@zephyrbot zephyrbot added area: UART Universal Asynchronous Receiver-Transmitter platform: NXP NXP labels Oct 6, 2025
Handle the case where there are multiple different kinds of UART on one
platform, the other UART driver select SERIAL_SUPPORT_ASYNC but LPUART
did not, causing build error in LPUART driver. Shield LPUART driver from
this case by introducing driver config to indicate that in fact LPUART
is the one enabling ASYNC.

Signed-off-by: Declan Snyder <[email protected]>
@decsny decsny force-pushed the fix/lpuart_multiple_uart_no_async branch from 1414fd4 to 79440f3 Compare October 6, 2025 13:32
Copy link

sonarqubecloud bot commented Oct 6, 2025

@hakehuang
Copy link
Contributor

@decsny #97022 fixed.

@nashif nashif removed the Hotfix Fix for issues blocking development, i.e. CI issues, tests failing in CI, etc. label Oct 8, 2025
@nashif
Copy link
Member

nashif commented Oct 8, 2025

how is this a hotfix? please do not use hotfix for bug fixes, hotfix should only be used for serious CI issues that block overall development, not a breakage on some hardware being tested downstream.

@decsny
Copy link
Member Author

decsny commented Oct 8, 2025

how is this a hotfix? please do not use hotfix for bug fixes, hotfix should only be used for serious CI issues that block overall development, not a breakage on some hardware being tested downstream.

It was blocking CI, did you read the description of the PR where I said it's fixing CI issues? it's not a hardware failure, it's a build failure, see linked issue. In fact I think honestly we don't care if this led strip sample fails on hardware very much at all

@decsny
Copy link
Member Author

decsny commented Oct 8, 2025

Although we probably could remove the hotfix now due to some other hotfix went in for the same issue I think, but originally this was a hotfix due to many PR blocked by CI due to this issue @nashif

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: UART Universal Asynchronous Receiver-Transmitter platform: NXP NXP
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tests: tests/drivers/build_all/led_strip : build failure on legacy kinetis platform
7 participants