Michal SimekandYann Gautier b1926f4c08 fix(zynqmp): workaround issue around cntpct_el0 ...

cntvct_el0 after power up has an architecturally UNKNOWN value.
In ZynqMP case the value is very high (e.g. 0xefffffe80d4de62d).
At best value should be 0 because it is used for time measuring when
systemd analyze command is called (via storing it in UEFI variables).
As a workaround for this issue use cntvoff_el2 to record offset from actual value which clears cntvct_el0.
There could be different way how to achieve this behavior but till that
time use this workaround to fix systemd analyze behavior.

Change-Id: Ie43096bb33bb0e02c8cac07f965610b4565e141c
Signed-off-by: Michal Simek <michal.simek@amd.com>

2025-07-15 09:48:29 +02:00

..

common

Merge "feat(zynqmp): remove pm_ioctl_set_sgmii_mode api" into integration

2023-11-06 09:21:54 +01:00

versal

feat(versal): enable errata management feature

2024-01-29 13:06:25 +00:00

versal_net

Merge changes from topic "enable_assertion" into integration

2023-11-06 17:55:20 +01:00

zynqmp

fix(zynqmp): workaround issue around cntpct_el0

2025-07-15 09:48:29 +02:00