On Mon, Apr 02, 2012 at 07:02:03PM -0700, Kuninori Morimoto wrote:
If board selects their CODEC driver, the driver will be forcefully included to kernel. And some of these are depend on extra config like I2C. I'm afraid about this kind of "forcefully select".
Of course we can create selectable Kconfig for each boards. but it is just complex..
I guess, yes. Though thinking about this further perhaps what we really want to do is provide a way to list all the CODEC drivers which can be supported by this driver and then have the driver select them all together, that way we don't have to keep adding Kconfig options for each individual device.
The driver isn't really particularly FSI specific either... the main thing I want to avoid is having to end up doing lots of this sort of little update on lots of platforms - it feels like we should be able to avoid having to add a Kconfig entry for every single combination of CPU and CODEC unless there's specific code to support that combination somehow (like when the CODEC has fancy clocking arrangements).