On 01/08/2010 01:00 PM, Tony Lindgren wrote:
* Philip Balister<philip@xxxxxxxxxxxx> [100108 07:35]:
I am trying to work out how to use the new pinmux code on my
Overo+Summit system. I have a recent git running with the new pinmux
code built. I am trying to configure the mcspi1_clk pin on the
expansion connector as gpio_171 with the following:
root@overo:~# dmesg |grep mux
Kernel command line: console=ttyS2,115200n8 vram=12M
omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y
omapdss.def_display=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3
rootwait omap_mux=mcspi1_clk.gpio_171=0x0
And this is what happens :(
mux: Could not set signal mcspi1_clk
mux: Setting signal i2c3_scl.i2c3_scl 0x0118 -> 0x0100
Any suggestions?
Sounds like the cmdline options got broken by some changes
I did to limit everything to happen as __init..
Can you please try the following patch?
Regards,
Tony
Tested-by: Philip Balister <philip@xxxxxxxxxxxx>
--
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
