* Jan Weitzel <[email protected]> [110719 04:40]: > Prepare board-omap4panda for joing other similar boards. > Split common stuff into board-omap4panda-common. > > MUX: board_mux and omap4_panda_mux > omap4_common_preinit: for muxing > omap4_common_init: all common devices > struct panda_board_data: gpios, omap_board_data, i2c_board_info ... > > some inititialisation check if omap4_panda_config entry is valid > i2c_2_board_speed == 0 -> i2c_2 not used > hup_power_gpio == -EINVAL -> gpio not used
This should probably be split into two patches: - Prepare things for panda common code - Move panda common code That way we can see from the patches what actually changes. Might also make sense to do it the other way around for the two patches. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
