summaryrefslogtreecommitdiff
path: root/scripts/env2string.awk
diff options
context:
space:
mode:
authorNeil Armstrong <[email protected]>2025-11-20 09:12:52 +0100
committerNeil Armstrong <[email protected]>2025-11-20 09:17:58 +0100
commit60a99d5ca374c83c0118f2634a7fcf4cc707b965 (patch)
tree245cf232f7a3e37f522ab84a22d4fecd79cee9d6 /scripts/env2string.awk
parenta264c0454b8ddd8c5ac0ed29623c72f65ec4d53f (diff)
Introduce the Generic System Interconnect Subsystem
Let's introduce the Generic System Interconnect subsystem based on the counterpart Linux framework which is used to vote for bandwidth across multiple SoC busses. Documentation for the Linux Generic System Interconnect Subsystem can be found at [1]. Each bus endpoints are materialised as "nodes" which are linked together, and the DT will specify a pair of nodes to enable and set a bandwidth on the route between those endpoints. The hardware resources that provide those nodes and provides the way to vote for the bandwidth are called "providers". The Interconnect uclass code is heavily based on the Linux one, with some small differences: - nodes are allocated as udevices instead of Linux idr_alloc() - tag management is minimal, only normal xlate is supported - getting nodes states at probe is not implemented - providers are probed on demand while the nodes links are traversed - nodes are populated on bind - id management is simplified, static IDs and dynamics IDs can be used - identical consume API as Linux, only implementation differs Fully tested with associated DM test suite. [1] https://docs.kernel.org/driver-api/interconnect.html Link: https://patch.msgid.link/[email protected] Signed-off-by: Neil Armstrong <[email protected]>
Diffstat (limited to 'scripts/env2string.awk')
0 files changed, 0 insertions, 0 deletions