[APPLIED] [PATCH] omap: mux: fix multipath gpio handling

2010-07-07 Thread Tony Lindgren
This patch has been applied to the linux-omap by youw fwiendly patch wobot. Branch in linux-omap: for-next Initial commit ID (Likely to change): 916c48fbec05b4718b4fd447f634725ced6cc9e7 PatchWorks http://patchwork.kernel.org/patch/110284/ Git (Likely to change, and takes a while to get mirrored

Re: [PATCH] omap: mux: fix multipath gpio handling

2010-07-06 Thread Grazvydas Ignotas
On Tue, Jul 6, 2010 at 4:25 PM, Tony Lindgren wrote: > * Grazvydas Ignotas [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

Re: [PATCH] omap: mux: fix multipath gpio handling

2010-07-06 Thread Tony Lindgren
* Grazvydas Ignotas [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

[PATCH] omap: mux: fix multipath gpio handling

2010-07-05 Thread Grazvydas Ignotas
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 inst