hisilicon-opensdk: bump 7fa06b2 → 28a30ca (frame-ts FEND extension)#2126
Merged
Conversation
Picks up openhisilicon PR #178 (openhisilicon/issues/176, /177): - ISP_FEND second event source on /dev/openipc-frame-ts alongside MIPI_FS; pairing both gives sensor readout duration directly. ABI extended (event_type field, OPENIPC_FT_IOC_SET_EVENT_MASK ioctl). - Edge-detect on the level-held raw vsync / FEND bits in ISP_ISR and mipi_rx_interrupt_route (V4 + cv500) — fixes a previously-shipped cherry-pick that fired zero FEND events on real silicon. - Per-channel ring 64 → 256 (≈ 0.5 s buffer at 480 Hz of FS+FEND). - Split "dropped" counter: dropped = ring overflow (data loss), coalesced = dedupe rejects (expected). New GET_COALESCED ioctl. End-user impact: with this bump, smolrtsp / majestic (widgetii/majestic PR #83 already shipping) can issue NTP-anchored RTCP Sender Reports correctly across the whole HiSi V4 + cv500 lineup. FEND consumers (ROS fusion, latency telemetry) can also start computing per-frame sensor readout duration without an external probe. Validated empirically on ev300 (V4, IMX335) and av300 (cv500, IMX415) across the full sensor mode lineup — zero drops 21–240 fps, clean readout times scaling linearly with active row count (IMX335 4.4 ms at 480 rows up to 28.4 ms at 1944 rows; IMX415 31.5 ms at 4M).
widgetii
added a commit
that referenced
this pull request
May 23, 2026
Merged
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Picks up OpenIPC/openhisilicon#178 (closes openhisilicon#176, openhisilicon#177):
/dev/openipc-frame-tsalongsideMIPI_FS. Pairing both events frame-by-frame gives sensor readout duration directly (wall_ns[FEND] − wall_ns[FS]).event_typefield instruct openipc_frame_ts_event, newOPENIPC_FT_IOC_SET_EVENT_MASKandOPENIPC_FT_IOC_GET_COALESCEDioctls.ISP_ISRandmipi_rx_interrupt_route(V4 + cv500) — fixes a previously-shipped cherry-pick that fired zero FEND events on real silicon.droppedcounter intodropped(ring overflow → data loss) andcoalesced(dedupe rejects → expected at high IRQ rates). NewGET_COALESCEDioctl.End-user impact
With this bump, widgetii/majestic#83 (already merged) can correctly anchor RTCP Sender Reports to wall-clock time across the HiSilicon V4 + cv500 lineup — RTSP clients see NTP-anchored timestamps instead of pipeline-relative ones (correct multi-camera sync, correct seek in recordings).
FEND consumers (ROS 2 multi-sensor fusion, PixelPilot-style per-segment latency telemetry, evidence chains) can also compute per-frame sensor readout duration without an external probe.
Test plan
samples/openipc_frame_ts/.🤖 Generated with Claude Code