drivers: net: Select UART_INTERRUPT_DRIVEN with UART RCP communication #85090
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lmajewski
force-pushed
the
openthread-rcp-UART_INTERRUPT_DRIVEN-fix
branch
from
ab86267 to
f4e3560
Compare
|
@xavraz @dleach02 @JA-NXP @decsny @mmahadevan108 |
pdgendt
reviewed
Feb 7, 2025
…ation The Openthread communication with RCP via UART (with HDLC protocol) is performed with serial driver using interrupts. As it was tested with echo_client sample program, the CONFIG_SHELL_BACKEND_SERIAL_API_INTERRUPT_DRIVEN is defined by default for it. This config selects aforementioned UART_INTERRUPT_DRIVEN. Problem starts when somebody wants to integrated the driver as a standalone one (without echo_client) as a part of user application. In this situation the UART_INTERRUPT_DRIVEN is not defined by default and there is no serial communication between RCP and HOST devices. Signed-off-by: Lukasz Majewski <lukma@denx.de>
lmajewski
force-pushed
the
openthread-rcp-UART_INTERRUPT_DRIVEN-fix
branch
from
f4e3560 to
b0aed4c
Compare
pdgendt
approved these changes
Feb 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Openthread communication with RCP via UART (with HDLC protocol) is performed with serial driver using interrupts. As it was tested with echo_client sample program, the
CONFIG_SHELL_BACKEND_SERIAL_API_INTERRUPT_DRIVEN is defined by default for it. This config selects aforementioned UART_INTERRUPT_DRIVEN.
Problem starts when somebody wants to integrated the driver as a standalone one (without echo_client) as a part of user application. In this situation the UART_INTERRUPT_DRIVEN is not defined by default and there is no serial communication between RCP and HOST devices.