Skip to content

Conversation

@JordanYates
Copy link
Contributor

Extract the user pipe setup and claim/release logic so that it can be re-used by other software modules, if the AT shell is not used. Ideally the chat instance would live within the modem_at_user_pipe.c and be handed out by modem_at_user_pipe_claim, but the current chat API doesn't make this possible.

Extract the user pipe setup and claim/release logic so that it can be
re-used by other software modules, if the AT shell is not used. Ideally
the chat instance would live within the `modem_at_user_pipe.c` and be
handed out by `modem_at_user_pipe_claim`, but the current chat API
doesn't make this possible.

Signed-off-by: Jordan Yates <jordan@embeint.com>
@JordanYates JordanYates force-pushed the 250918_modem_chat_extract branch from c8f822b to 07130e8 Compare September 18, 2025 08:24
@sonarqubecloud
Copy link

Copy link
Contributor

@bjarki-andreasen bjarki-andreasen left a comment

Choose a reason for hiding this comment

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

Neat, one of the last things I wanted to do before I got assigned new tasks was to make the modem_chat itself shareable, so the driver would create one chat instance, and that could be used directly by multiple components.

@henrikbrixandersen henrikbrixandersen merged commit c0a2928 into zephyrproject-rtos:main Sep 22, 2025
26 checks passed
@JordanYates JordanYates deleted the 250918_modem_chat_extract branch September 23, 2025 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Modem Drivers area: Modem Release Notes To be mentioned in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants