On Thu, Jul 08, 2021 at 04:58:43PM +0200, Greg KH wrote: > Ok, what "model" would be better? We need a "base object" that has > solid lifecycle rules. Right now we do have that, but it's just not the > easiest to use for complex objects where we have multiple objects with > different lifecycles that all interact together. The v4l example is the > best, but the input layer also has this type of issue. Audio too, the hardware is very similar v4l here with a lot of mix'n'match of separate devices to make one user visible thing which is itself exposed via multiple device nodes.