Lines Matching refs:devlink
4 devlink is an API to expose device information and resources not directly
13 in devlink core, but don't allow registration of most sub-objects once
14 the main devlink object is itself registered. The newer ``devl_*`` APIs assume
15 the devlink instance lock is already held. Drivers can take the instance
16 lock by calling ``devl_lock()``. It is also held all callbacks of devlink
19 Drivers are encouraged to use the devlink instance lock for their own needs.
21 Drivers need to be cautious when taking devlink instance lock and
29 devlink instances created underneath. In that case, drivers should make
33 lock of both nested and parent instances at the same time, devlink
39 - ``devl_nested_devlink_set()`` - called to setup devlink -> nested
40 devlink relationship (could be user for multiple nested instances.
42 nested devlink relationship.
44 nested devlink relationship.
46 The nested devlink info is exposed to the userspace over object-specific
47 attributes of devlink netlink.
52 The following pages describe various interfaces available through devlink in
58 devlink-dpipe
59 devlink-health
60 devlink-info
61 devlink-flash
62 devlink-params
63 devlink-port
64 devlink-region
65 devlink-resource
66 devlink-reload
67 devlink-selftests
68 devlink-trap
69 devlink-linecard
70 devlink-eswitch-attr
75 Each driver that implements ``devlink`` is expected to document what