Re: [PATCH v2 1/5] driver core: add a faux bus for use when a simple device/bus is needed
From: Greg Kroah-Hartman
Date: Thu Feb 06 2025 - 09:30:17 EST
On Tue, Feb 04, 2025 at 10:31:46AM -0500, Alan Stern wrote:
> On Tue, Feb 04, 2025 at 12:09:13PM +0100, Greg Kroah-Hartman wrote:
> > 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.
> >
> > Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> > ---
>
>
> > +/**
> > + * faux_device_create - create and register a faux device and driver
> > + * @name: name of the device and driver we are adding
> > + * @faux_ops: struct faux_driver_ops that the new device will call back into, can be NULL
> > + *
> > + * Create a new faux device and driver, both with the same name, and
> > + * register them in the driver core properly.
>
> Along the same lines as Danilo's comment, this routine does not create a
> new driver any more.
Thanks, I'll re-read all the documentation and make sure it all makes
sense now.
greg k-h