Skip to content

[alert,dv] Make the base driver explicit that it's just for alerts#29536

Draft
rswarbrick wants to merge 2 commits intolowRISC:masterfrom
rswarbrick:alert-base-driver-specificity
Draft

[alert,dv] Make the base driver explicit that it's just for alerts#29536
rswarbrick wants to merge 2 commits intolowRISC:masterfrom
rswarbrick:alert-base-driver-specificity

Conversation

@rswarbrick
Copy link
Copy Markdown
Contributor

@rswarbrick rswarbrick commented Mar 22, 2026

NOTE: This is in draft because it depends on #29504 (the first commit). Once that is merged, this PR only contains the final commit

This was already the case (because the esc_*_driver subclasses didn't actually use the code in alert_esc_base_driver), but it was a little tricky to understand.

@rswarbrick rswarbrick added Component:DV DV issue: testbench, test case, etc. IP:alert_handler labels Mar 22, 2026
The two types of interface are pretty unrelated and the existing code
had some strange corners. Make things more explicit and change
esc_receiver_driver and esc_sender_driver to derive directly from
dv_base_driver instead of alert_esc_base_driver.

Signed-off-by: Rupert Swarbrick <[email protected]>
This was already the case (because the esc_*_driver subclasses didn't
actually use the code in alert_esc_base_driver), but it was a little
tricky to understand.

Signed-off-by: Rupert Swarbrick <[email protected]>
@rswarbrick rswarbrick force-pushed the alert-base-driver-specificity branch from a60b93f to 08eb66e Compare March 30, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Component:DV DV issue: testbench, test case, etc. IP:alert_handler

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant