Conversation
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.
rp1-ptp-ppsadds a self-contained Raspberry Pi utility for the RP1 EthernetPHC. It uses the standard Linux PTP interface and
testptp, supports selectedBCM GPIOs, and can capture two independent rising-edge EXTTS channels while
producing one PEROUT signal. The package includes
testptp, the guardedcommand-line runtime, systemd units, an example configuration, and setup
instructions. It does not require raspi-config.
The runtime checks the active PHC's capabilities before mapping pins, prints a
non-actuating plan by default, and requires an explicit
--executefor GPIOoperations. The continuous services own and clean their PTP mappings. The
second input channel currently requires active PEROUT because the RP1 timestamp
latch is shared.
The kernel support is proposed separately in
raspberrypi/linux PR 7659.
The utility requires a driver exposing two EXTS channels, one PEROUT channel,
and 28 programmable pins.
Validation:
raspberrypi/utilsCMake build succeeds on ARM64.testptp -hcommand succeeds.units, documentation, and example configuration.
systemd-analyze verifyaccepts both generated service units.The simultaneous two-input physical path has not yet been qualified. Earlier
hardware checks exercised input and output sequentially. No board-level
accuracy or jitter guarantee is claimed.