fix: update shmbridge testcase#446
Conversation
smuppand
left a comment
There was a problem hiding this comment.
The direction is good: this expands shmbridge from a simple qcom_scm presence/log check into stronger runtime validation for sysfs, DT, platform driver registration, binding, attributes, and uevent information.
A few changes are needed
07c1148 to
53fe1d3
Compare
smuppand
left a comment
There was a problem hiding this comment.
A few updates are needed for the readme. Once those are taken care of, we can proceed with the merge.
| | 4 | **Driver-to-device binding** | Symlinks under `/sys/bus/platform/drivers/qcom_scm/` | Yes | | ||
| | 5 | **sysfs attribute readability** | `/sys/module/qcom_scm/parameters/*` | Yes | | ||
| | 6 | **Device uevent / modalias** | `<bound_device>/uevent` | Informational | | ||
| | 7 | **TEE / TrustZone device node** | `/dev/tee0`, `/dev/teepriv0` | Informational | |
There was a problem hiding this comment.
The bold marker is not closed, and /dev/tee0, /dev/teepriv0, CONFIG_TEE should be code-formatted.
There was a problem hiding this comment.
There is ** added in the right? Can you please tell what needs to be updated?
This test validates the presence, registration, and correct runtime state of the qcom_scm driver on the target device Signed-off-by: Vamsee Narapareddi <vnarapar@qti.qualcomm.com>
|
@vnarapar Could you update the commit message to include the reason for these changes? |
This test validates the presence, registration, and correct runtime state of the qcom_scm driver on the target device