On Wed, Aug 08, 2012 at 12:41:20PM +0300, Peter Ujfalusi wrote: > +Required properties: > +- compatible : must be "ti,twl4030-audio" So, as I mentioned before I find this sort of direct mapping of the Linux device representation into the device tree really troubling. I'm just way too aware of the fact that even the Linux split of these things can change over time and often represents internal Linux considerations. > +-ti,hs_extmute: Use external mute for HS pop reduction > +-ti,hs_extmute_gpio: Use external GPIO to control the external mute > +-ti,hs_extmute_disable_level: The desired level of the GPIO line when the > + external mute is disabled. valuse: 0 or 1 This doesn't seem like something that should be in the CODEC driver really, there's a general need for something which can unmute controls at the end of the power up sequence and mute before power down. Also, if this is going to be part of the binding shouldn't we just omit the first property and simply check for the presence of the property which specifies the GPIO? > +#ifdef CONFIG_OF > + if (of_find_node_by_name(node, "codec")) > + return true; > +#endif This really seems like we should be stubbing out of_find_node_by_name() to return false in non-OF cases. > +#ifdef CONFIG_OF > + if (!of_property_read_u32(node, "ti,enable-vibra", &vibra) && vibra) > + return true; > +#endif Similarly here. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
