driver core: faux: only create the device if probe() succeeds

It's really hard to know if a faux device properly passes the callback
to probe() without having to poke around in the faux_device struc

driver core: faux: only create the device if probe() succeeds

It's really hard to know if a faux device properly passes the callback
to probe() without having to poke around in the faux_device structure
and then clean up. Instead of having to have every user of the api do
this logic, just do it in the faux device core itself.

This makes the use of a custom probe() callback for a faux device much
simpler overall.

Suggested-by: Kurt Borja <[email protected]>
Cc: Rafael J. Wysocki <[email protected]>
Reviewed-by: Kurt Borja <[email protected]>
Reviewed-by: Danilo Krummrich <[email protected]>
Link: https://lore.kernel.org/r/2025022545-unroasted-common-fa0e@gregkh
Signed-off-by: Greg Kroah-Hartman <[email protected]>

show more ...

driver core: add a faux bus for use when a simple device/bus is needed

Many drivers abuse the platform driver/bus system as it provides a
simple way to create and bind a device to a driver-specific

driver core: add a faux bus for use when a simple device/bus is needed

Many drivers abuse the platform driver/bus system as it provides a
simple way to create and bind a device to a driver-specific set of
probe/release functions. Instead of doing that, and wasting all of the
memory associated with a platform device, here is a "faux" bus that
can be used instead.

Reviewed-by: Jonathan Cameron <[email protected]>
Reviewed-by: Danilo Krummrich <[email protected]>
Reviewed-by: Lyude Paul <[email protected]>
Reviewed-by: Thomas Weißschuh <[email protected]>
Reviewed-by: Zijun Hu <[email protected]>
Link: https://lore.kernel.org/r/2025021026-atlantic-gibberish-3f0c@gregkh
Signed-off-by: Greg Kroah-Hartman <[email protected]>

show more ...