Skip to content

[Feature Request] Enable each stream buffer to use a different sbSEND_COMPLETED implementation #312

@RichardBarry

Description

@RichardBarry

Is your feature request related to a problem? Please describe.
sbSEND_COMPLETED is the macro that performs any processing necessary after data has been sent to a stream buffer. By default this will unblock a task if a task is waiting for data from the stream buffer. The application writer can provide their own definition that, for example, can raise an interrupt in another core when the stream buffer is used for core to core communication. However currently a single global definition of sbSEND_COMPLETED applies to every stream buffer, enforcing each stream buffer to behave in the same way.

Describe the solution you'd like
While the above can be worked around within the application it would be an improvement if each stream buffer can define its own sbSEND_COMPLETED equivalent, and only use the default implementation when a stream buffer specific implementation is not supplied.

Additional context
See https://forums.freertos.org/t/messagebuffers-for-core-to-core-communication/12318

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions