-
Notifications
You must be signed in to change notification settings - Fork 8.1k
[Backport v4.1-branch] drivers: i3c: fix multiple issues in common code, shell, and CCC #86788
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
base: v4.1-branch
Are you sure you want to change the base?
Conversation
There is an incorrect dynamic address setting for setaasa. The correct behavior is that the dynamic address should be assigned as a static address only when the CCC request returns success. This commit fixes the issue. Signed-off-by: Ren Chen <[email protected]> (cherry picked from commit 373771c)
The errno for format 2 of the getstatus ccc always returns an error. The check for the invalid defining byte should use the "AND" operation instead of "OR." Additionally, the first byte of the ibi tir sending request is ignored due to the incorrect argument count. This commit fixes both issues. Signed-off-by: Ren Chen <[email protected]> (cherry picked from commit 20dbf4d)
This commit adds the missing data length(=0) for entas ccc. Signed-off-by: Ren Chen <[email protected]> (cherry picked from commit 9388349)
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
|
Please retry analysis of this Pull-Request directly on SonarQube Cloud |
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
|
@XenuIsWatching can you make an issue for this? |
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
Backport 9388349~3..9388349 from #86534.