diff options
| author | Danilo Krummrich <dakr@kernel.org> | 2026-07-17 15:39:24 +0200 |
|---|---|---|
| committer | Danilo Krummrich <dakr@kernel.org> | 2026-07-17 15:40:49 +0200 |
| commit | 2b74f1f2024486c7a81915528b6aa7f8f5daa021 (patch) | |
| tree | e724f3e2aef4f8cad737adcc53b4ab751a56da33 /rust/kernel/firmware.rs | |
| parent | f9e7a7564834af3e1239fbb9a4161f448edd04fa (diff) | |
| parent | 1226304062453754dd8fe7ec3f2656d600e9efe0 (diff) | |
| download | linux-next-2b74f1f2024486c7a81915528b6aa7f8f5daa021.tar.gz linux-next-2b74f1f2024486c7a81915528b6aa7f8f5daa021.zip | |
Merge patch series "software node: provide support for fw_devlink"
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com> says:
Currently only devicetree systems have their devices' probe ordered
against their suppliers automatically by fw_devlink. Software nodes have
lately been used extensively treewide to describe references to resource
suppliers: most notably, the GPIO subsystem uses it in many places. Now
that the conversion of "dangling" GPIO chip software nodes to using real
links is almost done, it makes sense to ensure no needless probe
deferrals by implementing the add_links() callback from the fwnode
interface.
This series extends software node support to use fw_devlink and adds test
coverage for the new behaviour.
Caveats: a supplier software node must be registered before the consumer
device is added, If the swnode is registered after the consumer was added,
add_links() has already run and set FWNODE_FLAG_LINKS_ADDED, so the late
supplier is missed. Graph/remote- endpoint ordering is left out for now as
well as there are no known users.
Link: https://patch.msgid.link/20260713-swnode-fw-devlink-v4-0-d4f2dee27ad9@oss.qualcomm.com
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'rust/kernel/firmware.rs')
0 files changed, 0 insertions, 0 deletions
