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

drivers: i3c: add support for setaasa initialization #78117

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

XenuIsWatching
Copy link
Member

Adds a new DTS prop for i3c devices as support for the CCC SETAASA requires prior knowledge of the target if it supports it according to i3c spec v1.1.1 section 5.19.3.23.

This will be used as an optimization for bus initialization.

Adds a new DTS prop for i3c devices as support for the CCC SETAASA
requires prior knowledge of the target if it supports it according
to i3c spec v1.1.1 section 5.19.3.23.

This will be used as an optimization for bus initialization.

Signed-off-by: Ryan McClelland <[email protected]>
Comment on lines +65 to +69
supports-setaasa:
type: boolean
description: |
Indicates if the device supports the CCC SETAASA. If true, it will
be used as an optimization for bus initialization.
Copy link
Member

Choose a reason for hiding this comment

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

nit: if more supports-* are required in the future, a bit field could be more future-proof, but not sure if it can be the case.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah... it definitely could and that was something was thinking about, but that could come when more "supports" are implemented rather than using an inefficient bool for each of them.

@nashif nashif merged commit 9d345fc into zephyrproject-rtos:main Sep 10, 2024
23 checks passed
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.

5 participants