You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Circuit-breaker is per-instance, not per-camera**: Each `struct ds5`has its own counter. Since userspace sends HW reset to one instance (typically Depth at `9-001a`), this naturally tracks per-camera. Peer instances aren't reset independently.
60
+
-**Circuit-breaker is per-camera, shared across instances**: The tracking fields live in `struct ds5_dev`, so all `struct ds5`instances for the same physical camera share a single counter and breaker state. If any instance (typically Depth at `9-001a`) trips the breaker, further HW reset requests from any instance for that camera are rejected until the breaker auto‑clears.
61
61
-**Return -EBUSY for tripped breaker, -EAGAIN for cooldown**: Distinct error codes let userspace distinguish "permanently failed" from "try again later".
62
62
-**Auto-clear after 60s inactivity**: Avoids permanent lockout. If the camera recovers externally (e.g., power cycle), the driver will accept resets again.
63
63
-**Phase 1 dual-camera is diagnostic only**: No blocking behavior added — just logging. If field data shows disruption, we can add a sibling-streaming gate in a future commit.
0 commit comments