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

[chip-test] chip_sw_pwrmgr_escalation_reset #21451

Closed
9 tasks
johngt opened this issue Feb 15, 2024 · 1 comment
Closed
9 tasks

[chip-test] chip_sw_pwrmgr_escalation_reset #21451

johngt opened this issue Feb 15, 2024 · 1 comment
Labels
Component:ChipLevelTest Used to filter the chip-level test backlog IP:pwrmgr Priority:P2 Priority: medium SiVal:Autogen Generated by script

Comments

@johngt
Copy link

johngt commented Feb 15, 2024

Test point name

chip_sw_pwrmgr_escalation_reset

Host side component

Rust?

Opentitantool infrastructure implemented

Yes

Silicon Validation (SiVal)

Yes

Emulation targets

  • None
  • CW310
  • Hyperdebug + CW310

Contact person

Checklist

Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

  • Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
  • Device-side (C) component developed
  • Bazel build rules developed
  • Host-side component developed
  • Test added to dvsim nightly regression (and passing at time of checking)
  • For SiVal test cases, test is running relevant FPGA or silicon regression
@johngt johngt added Component:ChipLevelTest Used to filter the chip-level test backlog IP:pwrmgr Priority:P2 Priority: medium SiVal:Autogen Generated by script labels Feb 15, 2024
@matutem
Copy link
Contributor

matutem commented Feb 23, 2024

I don't know why this issue was created: in the description at https://cs.opensource.google/opentitan/opentitan/+/master:hw/top_earlgrey/data/ip/chip_pwrmgr_testplan.hjson;drc=2d6a8ad26708e4c2681c8ddc2a0fa1c911a4461d;l=486 it says clearly This is not suitable for sival, and in si_stage it is marked as None. Perhaps these should be used to filter out what seems to be a flow that detects missing test items? I will similarly close other similar issues.

@matutem matutem closed this as completed Feb 23, 2024
@jwnrt jwnrt changed the title [chip-test, pwrmgr] chip_sw_pwrmgr_escalation_reset [chip-test] chip_sw_pwrmgr_escalation_reset Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component:ChipLevelTest Used to filter the chip-level test backlog IP:pwrmgr Priority:P2 Priority: medium SiVal:Autogen Generated by script
Projects
None yet
Development

No branches or pull requests

2 participants