On Fri, Aug 07, 2015 at 04:03:08PM -0400, Felix Kuehling wrote: > 1. GPU driver gets initialized, detects a GPU with audio co-processor (ACP) > 2. GPU driver registers mfd_cell for the ACP device using > mfd_add_hotplug_devices > * It's not really hot-plug, but the mem_base, irq_base, irq_domain > parameters don't make sense for us All those should be optional... > 3. Platform_data in the MFD cell contains audio driver-specific data, > function pointers, etc. for the audio driver to use Note that a MFD knows that its parent is the core device so it can just look at the driver data of the parent unless things vary per child. > 4. Audio driver binds to platform device created by > mfd_add_hotplug_devices based on driver name > Or do we have to convert our GPU device to be an MFD cell itself, a peer > of the ACP cell? If they're all part of the same block of hardware that'd be more normal, but it all depends on what the code looks like and what the relevant maintainers think.
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
