On Tue, Jul 6, 2010 at 4:25 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > * Grazvydas Ignotas <notasas@xxxxxxxxx> [100705 23:00]: >> OMAP3530 CBB package can have GPIO126 muxed on 2 pins: mmc1_dat4 and >> cam_strobe. This causes a problem with current multipath GPIO mux >> handling, which muxes both pins as GPIO126 and makes the GPIO unusable. >> >> Fix this by not muxing any pins if multipath GPIO is detected and >> just print a warning instead. It's up to board files to set correct >> mux using omap_mux_init_signal and pin name. > > This looks good to me. Are you OK if we merge it during the upcoming > merge window? Kind of worried that we might break some other boards > that rely on the first GPIO getting muxed.. Yeah that should be fine, no need to rush. -- 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
