On Thu, Mar 31, 2016 at 10:37:20AM +0100, Jose Abreu wrote: > On 29-03-2016 19:22, Mark Brown wrote: > > If you want to add a new platform driver you need to add a new platform > > driver, not shove the code into an existing driver for a seperate IP. > I can separate the platform driver into a new file but they will have to be > compiled into the same module as the new additions to the i2s driver depend on > functions of the platform driver (see i2s_irq_handler()). Or should I divide No, that's not at all acceptable. The Designware IP is not specific to your system, you can't make it depend on your platform driver. The kernel needs to work on other people's systems too. You need to work through and/or extend the abstractions the framework provides to separate the drivers for different IPs. > this into two modules and add a Kconfig option to the platform driver? Besides > this I first wanted the driver to be compiled into the same module so that it is > compatible with kernel 3.18 where simple audio card requires that platform > driver == cpu driver. That's not OK upstream, we're working on the current kernel not on random old kernels. We don't carry compatibility code to enable current kernel code to be run on years old kernels.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
