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

open-amp: resource table: Add support for vendor-specific features #87296

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

iuliana-prodan
Copy link
Collaborator

Add support for vendor-specific features in the remote processor resource table.
This is configurable based on the length of the vendor-specific resource.

For header we are using struct fw_rsc_vendor from OpenAMP and an array of words to store vendor-specific features supported by the firmware. The supported features will be defined in
CONFIG_OPENAMP_RSC_TABLE_VENDOR_DATA_FEATURES_X, where X represents the number of words needed (1 to 4).

This enhancement allows better flexibility for remote processors requiring custom features configurations.

Add support for vendor-specific features in the remote processor
resource table.
This is configurable based on the length of the vendor-specific resource.

For header we are using struct fw_rsc_vendor from OpenAMP and an array
of words to store vendor-specific features supported by the firmware.
The supported features will be defined in
CONFIG_OPENAMP_RSC_TABLE_VENDOR_DATA_FEATURES_X, where X represents
the number of words needed (1 to 4).

This enhancement allows better flexibility for remote processors requiring
custom features configurations.

Signed-off-by: Iuliana Prodan <[email protected]>
Copy link
Member

@uLipe uLipe left a comment

Choose a reason for hiding this comment

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

I have a question regarding turning this option on and off, otherwise looks good to me.

config OPENAMP_RSC_TABLE_VENDOR_RSC_LENGTH
int "Vendor specific length of the resource"
default 0
range 0 4
Copy link
Member

Choose a reason for hiding this comment

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

Question instead of using the size to actually reserve space in the rsc_table, why not create a specific option let's ADD_VENDOR_SPEFICIC_AREA?

I'm afraid that implementors may use for example 0 - sized values and it silently have hard time to debug when this value is badly populated

Having a switch like option enforces the implementor to search the documentation to refer the "right" way to populate the vendor reserved area.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants