diff options
| author | Igor Skalkin <[email protected]> | 2021-08-03 13:10:19 +0000 |
|---|---|---|
| committer | Sudeep Holla <[email protected]> | 2021-08-05 09:23:23 +0000 |
| commit | c92c3e382ebd2382b26a41e312a266a40c4fb05c (patch) | |
| tree | a3bb88ac8bcecf0ad212941d7a1e806ced050fdb /tools/perf/scripts/python/check-perf-trace.py | |
| parent | firmware: arm_scmi: Make shmem support optional for transports (diff) | |
| download | kernel-c92c3e382ebd2382b26a41e312a266a40c4fb05c.tar.gz kernel-c92c3e382ebd2382b26a41e312a266a40c4fb05c.zip | |
firmware: arm_scmi: Add method to override max message number
The maximum number of simultaneously pending messages is a transport
specific quantity that is usually described statically in struct scmi_desc.
Some transports, though, can calculate such number only at run-time after
some initial transport specific setup and probing is completed; moreover
the resulting max message numbers could also be different between rx and
tx channels.
Add an optional get_max_msg() operation so that a transport can report more
accurate max message numbers for each channel type.
The value in scmi_desc.max_msg is still used as default when transport does
not provide any get_max_msg() method.
Link: https://lore.kernel.org/r/[email protected]
Co-developed-by: Peter Hilber <[email protected]>
Co-developed-by: Cristian Marussi <[email protected]>
Signed-off-by: Igor Skalkin <[email protected]>
[ Peter: Adapted patch for submission to upstream. ]
Signed-off-by: Peter Hilber <[email protected]>
[ Cristian: refactored how get_max_msg() is used to minimize core changes ]
Signed-off-by: Cristian Marussi <[email protected]>
Signed-off-by: Sudeep Holla <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions
