Skip to content
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

Add RPMsg API to get buffer size #565

Merged
merged 3 commits into from
Apr 9, 2024
Merged

Commits on Mar 18, 2024

  1. rpmsg: Add API for retrieving message buffer sizes

    Add an RPMsg API to get the buffer sizes supported by the backing
    transport layer. Add hooks so that transport layers can register
    functions to provide this data.
    
    Signed-off-by: Andrew Davis <afd@ti.com>
    glneo committed Mar 18, 2024
    Configuration menu
    Copy the full SHA
    b308ff3 View commit details
    Browse the repository at this point in the history
  2. rpmsg_virtio: Connect rpmsg get buffer for the virtio transport layer

    RPMsg provides functions to get a transport's backing buffer sizes.
    Connect this up for the virtio transport here.
    
    Signed-off-by: Andrew Davis <afd@ti.com>
    glneo committed Mar 18, 2024
    Configuration menu
    Copy the full SHA
    49760b0 View commit details
    Browse the repository at this point in the history
  3. apps: Convert examples to rpmsg_get_{tx,rx}_buffer_size()

    The contents of app() in these examples is given a rpmsg_device. We should
    not have to know about the backing transport layer. We assume it is virtio
    and call into the virtio layer to get the buffer size. This information is
    now available from the rpmsg layer. Use those functions to make the app()
    agnostic to the backing layer.
    
    Signed-off-by: Andrew Davis <afd@ti.com>
    glneo committed Mar 18, 2024
    Configuration menu
    Copy the full SHA
    d5166b5 View commit details
    Browse the repository at this point in the history