-
Notifications
You must be signed in to change notification settings - Fork 8k
drivers: uart_mcux_lpuart: Handle multiple uart case #97051
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
base: main
Are you sure you want to change the base?
drivers: uart_mcux_lpuart: Handle multiple uart case #97051
Conversation
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]>
1414fd4
to
79440f3
Compare
|
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 |
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 |
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 ?