summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/gecko.py
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2025-09-03 16:51:12 -0700
committerJakub Kicinski <kuba@kernel.org>2025-09-03 16:51:12 -0700
commit648d628db536adfd8ae5e61b7a82908af8683918 (patch)
tree1c5816e763b5f20ae9d09a7c99b1b6f7c2c84001 /tools/perf/scripts/python/gecko.py
parent59aec9138f3056f0f6a521e065fd85853227bf45 (diff)
parentadbe2cfd8a93fdefb2bd238c1ccd22d2c40e8499 (diff)
Merge branch 'net-stmmac-allow-generation-of-flexible-pps-relative-to-mac-time'
Gatien Chevallier says: ==================== net: stmmac: allow generation of flexible PPS relative to MAC time When doing some testing on stm32mp2x platforms(MACv5), I noticed that the command previously used with a MACv4 for genering a PPS signal: echo "0 0 0 1 1" > /sys/class/ptp/ptp0/period did not work. This is because the arguments passed through this command must contain the start time at which the PPS should be generated, relative to the MAC system time. For some reason, a time set in the past seems to work with a MACv4. Because passing such an argument is tedious, consider that any time set in the past is an offset regarding the MAC system time. This way, this does not impact existing scripts and the past time use case is handled. Edit: But maybe that's not important and we can just change the default behavior to this. Example to generate a flexible PPS signal that has a 1s period 3s relative to when the command was entered: echo "0 3 0 1 1" > /sys/class/ptp/ptp0/period ==================== Link: https://patch.msgid.link/20250901-relative_flex_pps-v4-0-b874971dfe85@foss.st.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/gecko.py')
0 files changed, 0 insertions, 0 deletions