On Mon, May 12, 2008 at 12:57:11PM +1200, Ryan Mallon wrote:
> I am writing drivers to support ALSA SoC for an ARM based system. The
> system has an i2c codec. I want to use the new style driver for the
> codec driver, but I cannot get it to work properly. In my codec driver
> (sound/soc/codecs/tlv320aic2x.c) I have:
>
> static struct i2c_driver aic2x_i2c_driver = {
> .driver = {
> .name = "tlv320aic2x",
> .owner = THIS_MODULE,
> },
> .probe = aic2x_i2c_probe,
> .remove = aic2x_i2c_remove,
> };
>
> static int __init aic2x_init(void)
> {
> return i2c_add_driver(&aic2x_i2c_driver);
> }
>
> static void __exit aic2x_exit(void)
> {
> i2c_del_driver(&aic2x_i2c_driver);
> }
>
> module_init(aic2x_init);
> module_exit(aic2x_exit);
I belive that you need a bit of glue to bind your SoC system
to the codec and audio hardware. ASoC is littered with a number
of examples of how to do it.
> Finally, a stylistic question: Should the i2c_board_info (or similar)
> for a codec device be defined in the machine initialisation code
> (arch/arm/ directory), or in the sound/soc machine file?
--
Ben ([EMAIL PROTECTED], http://www.fluff.org/)
'a smiley only costs 4 bytes'
_______________________________________________
i2c mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/i2c
