It's really down to your objection to the use of 'struct driver'... For ASoC
support we only need the .name and .pm_ops, so there's really no possible
path forward otherwise.
It means that we cannot have a solution which is Intel specific into
core. If you has a standalone controller you do not need this.
Like I said, we have 3 options
Repeating the already discussed doesn't help. I have already told you the
constraint to work is not to add Intel specific change into core.
I have already said that expect the driver part I dont have objections
to rest of this series and am ready to merge
a) stay with platform devices for now. You will need to have a conversation
with Greg on this.
b) use a minimal sdw_master_device with a minimal 'struct driver' use.
c) use a more elaborate solution suggested in this patchset and yes that
means the Qualcomm driver would need to change a bit.
Pick one or suggest something that is implementable. The first version of
the patches was provided in October, the last RFC was provided on January
31, time's up. At the moment you are preventing ASoC integration from moving
forward.
In opensource review we go back and forth and we debate and come to a
common conclusion. Choosing a specific set of solutions and constraining
yourself to pick one does not help.
I have only _one_ constraint no platform specific change in core. If that
is satisfied I will go with it. Sorry but this is non-negotiable for me.
Ask yourself, do you need this intrusive core change if you had this
exact same controller(s) but only as standalone one...