With fw_devlink and with sync_state() callback features, there's a lot of device/device link related information that's not available in sysfs.
Exposing these details to user space can be very useful in understanding suspend/resume issues, runtime pm issues, probing issues, figuring out the modules that'd be needed for first stage init, etc. In fact, an earlier verion of this series was very helpful in debugging and validating the recent memory leak fix[1]. This series combines combines a bunch of patches I've sent before. I'm aware that I haven't added documentation for patch 1/2. I'm waiting on review to make sure the file location, name and values don't change before I add the documentation. This series is based on driver-core-next and [1] cherry-picked on top of it. [1] - https://lore.kernel.org/lkml/20200519063000.128819-1-sarava...@google.com/ v1->v2: Patch 1/4 - New patch Patch 2/4 - Fixed the warnings I saw before that were related to incorrect sysfs removal code when a device link is deleted. - Fixed error handling in device_link_add() - Split up flags into more meaningful files. - Added status file. Patch 3/4 - Fixed error handling that Greg pointed out before. Patch 4/4 - New patch Saravana Kannan (4): driver core: Remove unnecessary is_fwnode_dev variable in device_add() driver core: Expose device link details in sysfs driver core: Add state_synced sysfs file for devices that support it driver core: Add waiting_for_supplier sysfs file for devices .../ABI/testing/sysfs-devices-state_synced | 24 ++ .../sysfs-devices-waiting_for_supplier | 17 ++ drivers/base/core.c | 249 ++++++++++++++++-- drivers/base/dd.c | 22 ++ include/linux/device.h | 58 ++-- 5 files changed, 326 insertions(+), 44 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-devices-state_synced create mode 100644 Documentation/ABI/testing/sysfs-devices-waiting_for_supplier -- 2.26.2.761.g0e0b3e54be-goog