diff options
| author | Herve Codina <[email protected]> | 2024-10-14 14:46:32 +0200 |
|---|---|---|
| committer | Philipp Zabel <[email protected]> | 2024-10-24 12:09:33 +0200 |
| commit | 0426a920d6269cab3213f1f9eee1b5a91013441c (patch) | |
| tree | 62e738095908e6b087f1c9ea568b67805cd3991f /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | 86f134941a4b74489ee7b3d057aa23f2afcb1e45 (diff) | |
reset: mchp: sparx5: Map cpu-syscon locally in case of LAN966x
In the LAN966x PCI device use case, the syscon API cannot be used as
it does not support device removal [1]. A syscon device is a core
"system" device and not a device available in some addon boards and so,
it is not supposed to be removed. The syscon API follows this assumption
but this assumption is no longer valid in the LAN966x use case.
In order to avoid the use of the syscon API and so, support for removal,
use a local mapping of the syscon device.
Link: https://lore.kernel.org/all/[email protected]/ [1]
Signed-off-by: Herve Codina <[email protected]>
Reviewed-by: Steen Hegelund <[email protected]>
Reviewed-by: Philipp Zabel <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Philipp Zabel <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions