Loading Documentation/ABI/testing/sysfs-class-devlink 0 → 100644 +126 −0 Original line number Diff line number Diff line What: /sys/class/devlink/.../ Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: Provide a place in sysfs for the device link objects in the kernel at any given time. The name of a device link directory, denoted as ... above, is of the form <supplier>--<consumer> where <supplier> is the supplier device name and <consumer> is the consumer device name. What: /sys/class/devlink/.../auto_remove_on Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file indicates if the device link will ever be automatically removed by the driver core when the consumer and supplier devices themselves are still present. This will be one of the following strings: 'consumer unbind' 'supplier unbind' 'never' 'consumer unbind' means the device link will be removed when the consumer's driver is unbound from the consumer device. 'supplier unbind' means the device link will be removed when the supplier's driver is unbound from the supplier device. 'never' means the device link will not be automatically removed when as long as the supplier and consumer devices themselves are still present. What: /sys/class/devlink/.../consumer Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file is a symlink to the consumer device's sysfs directory. What: /sys/class/devlink/.../runtime_pm Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file indicates if the device link has any impact on the runtime power management behavior of the consumer and supplier devices. For example: Making sure the supplier doesn't enter runtime suspend while the consumer is active. This will be one of the following strings: '0' - Does not affect runtime power management '1' - Affects runtime power management What: /sys/class/devlink/.../status Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file indicates the status of the device link. The status of a device link is affected by whether the supplier and consumer devices have been bound to their corresponding drivers. The status of a device link also affects the binding and unbinding of the supplier and consumer devices with their drivers and also affects whether the software state of the supplier device is synced with the hardware state of the supplier device after boot up. See also: sysfs-devices-state_synced. This will be one of the following strings: 'not tracked' 'dormant' 'available' 'consumer probing' 'active' 'supplier unbinding' 'unknown' 'not tracked' means this device link does not track the status and has no impact on the binding, unbinding and syncing the hardware and software device state. 'dormant' means the supplier and the consumer devices have not bound to their driver. 'available' means the supplier has bound to its driver and is available to supply resources to the consumer device. 'consumer probing' means the consumer device is currently trying to bind to its driver. 'active' means the supplier and consumer devices have both bound successfully to their drivers. 'supplier unbinding' means the supplier devices is currently in the process of unbinding from its driver. 'unknown' means the state of the device link is not any of the above. If this is ever the value, there's a bug in the kernel. What: /sys/class/devlink/.../supplier Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file is a symlink to the supplier device's sysfs directory. What: /sys/class/devlink/.../sync_state_only Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file indicates if the device link is limited to only affecting the syncing of the hardware and software state of the supplier device. This will be one of the following strings: '0' '1' - Affects runtime power management '0' means the device link can affect other device behaviors like binding/unbinding, suspend/resume, runtime power management, etc. '1' means the device link will only affect the syncing of hardware and software state of the supplier device after boot up and doesn't not affect other behaviors of the devices. Documentation/ABI/testing/sysfs-devices-consumer 0 → 100644 +8 −0 Original line number Diff line number Diff line What: /sys/devices/.../consumer:<consumer> Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: The /sys/devices/.../consumer:<consumer> are symlinks to device links where this device is the supplier. <consumer> denotes the name of the consumer in that device link. There can be zero or more of these symlinks for a given device. Documentation/ABI/testing/sysfs-devices-state_synced 0 → 100644 +24 −0 Original line number Diff line number Diff line What: /sys/devices/.../state_synced Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: The /sys/devices/.../state_synced attribute is only present for devices whose bus types or driver provides the .sync_state() callback. The number read from it (0 or 1) reflects the value of the device's 'state_synced' field. A value of 0 means the .sync_state() callback hasn't been called yet. A value of 1 means the .sync_state() callback has been called. Generally, if a device has sync_state() support and has some of the resources it provides enabled at the time the kernel starts (Eg: enabled by hardware reset or bootloader or anything that run before the kernel starts), then it'll keep those resources enabled and in a state that's compatible with the state they were in at the start of the kernel. The device will stop doing this only when the sync_state() callback has been called -- which happens only when all its consumer devices are registered and have probed successfully. Resources that were left disabled at the time the kernel starts are not affected or limited in any way by sync_state() callbacks. Documentation/ABI/testing/sysfs-devices-supplier 0 → 100644 +8 −0 Original line number Diff line number Diff line What: /sys/devices/.../supplier:<supplier> Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: The /sys/devices/.../supplier:<supplier> are symlinks to device links where this device is the consumer. <supplier> denotes the name of the supplier in that device link. There can be zero or more of these symlinks for a given device. Documentation/ABI/testing/sysfs-devices-waiting_for_supplier 0 → 100644 +17 −0 Original line number Diff line number Diff line What: /sys/devices/.../waiting_for_supplier Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: The /sys/devices/.../waiting_for_supplier attribute is only present when fw_devlink kernel command line option is enabled and is set to something stricter than "permissive". It is removed once a device probes successfully (because the information is no longer relevant). The number read from it (0 or 1) reflects whether the device is waiting for one or more suppliers to be added and then linked to using device links before the device can probe. A value of 0 means the device is not waiting for any suppliers to be added before it can probe. A value of 1 means the device is waiting for one or more suppliers to be added before it can probe. Loading
Documentation/ABI/testing/sysfs-class-devlink 0 → 100644 +126 −0 Original line number Diff line number Diff line What: /sys/class/devlink/.../ Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: Provide a place in sysfs for the device link objects in the kernel at any given time. The name of a device link directory, denoted as ... above, is of the form <supplier>--<consumer> where <supplier> is the supplier device name and <consumer> is the consumer device name. What: /sys/class/devlink/.../auto_remove_on Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file indicates if the device link will ever be automatically removed by the driver core when the consumer and supplier devices themselves are still present. This will be one of the following strings: 'consumer unbind' 'supplier unbind' 'never' 'consumer unbind' means the device link will be removed when the consumer's driver is unbound from the consumer device. 'supplier unbind' means the device link will be removed when the supplier's driver is unbound from the supplier device. 'never' means the device link will not be automatically removed when as long as the supplier and consumer devices themselves are still present. What: /sys/class/devlink/.../consumer Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file is a symlink to the consumer device's sysfs directory. What: /sys/class/devlink/.../runtime_pm Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file indicates if the device link has any impact on the runtime power management behavior of the consumer and supplier devices. For example: Making sure the supplier doesn't enter runtime suspend while the consumer is active. This will be one of the following strings: '0' - Does not affect runtime power management '1' - Affects runtime power management What: /sys/class/devlink/.../status Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file indicates the status of the device link. The status of a device link is affected by whether the supplier and consumer devices have been bound to their corresponding drivers. The status of a device link also affects the binding and unbinding of the supplier and consumer devices with their drivers and also affects whether the software state of the supplier device is synced with the hardware state of the supplier device after boot up. See also: sysfs-devices-state_synced. This will be one of the following strings: 'not tracked' 'dormant' 'available' 'consumer probing' 'active' 'supplier unbinding' 'unknown' 'not tracked' means this device link does not track the status and has no impact on the binding, unbinding and syncing the hardware and software device state. 'dormant' means the supplier and the consumer devices have not bound to their driver. 'available' means the supplier has bound to its driver and is available to supply resources to the consumer device. 'consumer probing' means the consumer device is currently trying to bind to its driver. 'active' means the supplier and consumer devices have both bound successfully to their drivers. 'supplier unbinding' means the supplier devices is currently in the process of unbinding from its driver. 'unknown' means the state of the device link is not any of the above. If this is ever the value, there's a bug in the kernel. What: /sys/class/devlink/.../supplier Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file is a symlink to the supplier device's sysfs directory. What: /sys/class/devlink/.../sync_state_only Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: This file indicates if the device link is limited to only affecting the syncing of the hardware and software state of the supplier device. This will be one of the following strings: '0' '1' - Affects runtime power management '0' means the device link can affect other device behaviors like binding/unbinding, suspend/resume, runtime power management, etc. '1' means the device link will only affect the syncing of hardware and software state of the supplier device after boot up and doesn't not affect other behaviors of the devices.
Documentation/ABI/testing/sysfs-devices-consumer 0 → 100644 +8 −0 Original line number Diff line number Diff line What: /sys/devices/.../consumer:<consumer> Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: The /sys/devices/.../consumer:<consumer> are symlinks to device links where this device is the supplier. <consumer> denotes the name of the consumer in that device link. There can be zero or more of these symlinks for a given device.
Documentation/ABI/testing/sysfs-devices-state_synced 0 → 100644 +24 −0 Original line number Diff line number Diff line What: /sys/devices/.../state_synced Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: The /sys/devices/.../state_synced attribute is only present for devices whose bus types or driver provides the .sync_state() callback. The number read from it (0 or 1) reflects the value of the device's 'state_synced' field. A value of 0 means the .sync_state() callback hasn't been called yet. A value of 1 means the .sync_state() callback has been called. Generally, if a device has sync_state() support and has some of the resources it provides enabled at the time the kernel starts (Eg: enabled by hardware reset or bootloader or anything that run before the kernel starts), then it'll keep those resources enabled and in a state that's compatible with the state they were in at the start of the kernel. The device will stop doing this only when the sync_state() callback has been called -- which happens only when all its consumer devices are registered and have probed successfully. Resources that were left disabled at the time the kernel starts are not affected or limited in any way by sync_state() callbacks.
Documentation/ABI/testing/sysfs-devices-supplier 0 → 100644 +8 −0 Original line number Diff line number Diff line What: /sys/devices/.../supplier:<supplier> Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: The /sys/devices/.../supplier:<supplier> are symlinks to device links where this device is the consumer. <supplier> denotes the name of the supplier in that device link. There can be zero or more of these symlinks for a given device.
Documentation/ABI/testing/sysfs-devices-waiting_for_supplier 0 → 100644 +17 −0 Original line number Diff line number Diff line What: /sys/devices/.../waiting_for_supplier Date: May 2020 Contact: Saravana Kannan <saravanak@google.com> Description: The /sys/devices/.../waiting_for_supplier attribute is only present when fw_devlink kernel command line option is enabled and is set to something stricter than "permissive". It is removed once a device probes successfully (because the information is no longer relevant). The number read from it (0 or 1) reflects whether the device is waiting for one or more suppliers to be added and then linked to using device links before the device can probe. A value of 0 means the device is not waiting for any suppliers to be added before it can probe. A value of 1 means the device is waiting for one or more suppliers to be added before it can probe.
