GPIO_113 default pinmux should be GPIO input (Mode 3)

Bug #988497 reported by Murat Belge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Ubuntu
New
Undecided
Unassigned

Bug Description

Generated and SD card with Linaro 12.03 for PandaBoard ES:

# uname -a
Linux panda-ah-jpeng 3.1.1-29-linaro-lt-omap #29~lt~ci~20120328002449+1332949706~4f7349b0-Ubuntu SMP PREEMPT armv7l armv7l armv7l GNU/Linux

The GPIO_113 pin is connected to the USER push button. However, this pin comes up as McBSP2 FSX (Mode 0) upon boot:

# cat /sys/kernel/debug/omap_mux/abe_mcbsp2_fsx
name: abe_mcbsp2_fsx.abe_mcbsp2_fsx (0x4a1000fc/0x0fc = 0x0100), b ac28, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_mcbsp2_fsx | mcspi2_cs0 | abe_mcasp_afsx | gpio_113 | usbb2_mm_txen | NA | NA | safe_mode

This pin should be muxed as GPIO input (with pull-up resistor enabled) as it is tied to the push button and PandaBoard ES manual says internal pull-up should be enabled. To set the pin muxing correctly, I use the following shell commands:

#echo 0x011B > /sys/kernel/debug/omap_mux/abe_mcbsp2_fsx
#cat abe_mcbsp2_fsx
name: abe_mcbsp2_fsx.gpio_113 (0x4a1000fc/0x0fc = 0x011b), b ac28, t NA
mode: OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE3
signals: abe_mcbsp2_fsx | mcspi2_cs0 | abe_mcasp_afsx | gpio_113 | usbb2_mm_txen | NA | NA | safe_mode

Revision history for this message
Chase Qi (chase-qi) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.