Hi,
The LED mapping for our TI AM335x based board is as follows --
{"gpio1_15", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED1r
{"gpio1_14", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED1g
{"gpio0_27", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED2r
{"gpio0_26", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED2g
{"gpio0_23", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED3r
{"gpio0_22", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED3g
{"gpio3_17", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED4r
{"gpio3_18", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED4g
{"gpio0_20", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED5r
{"gpio0_19", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED5g
{"gpio0_10", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED6r
{"gpio3_16", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED6g
{"gpio1_13", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED7r
{"gpio1_12", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED7g
{"gpio3_15", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED8r
{"gpio3_14", OMAP_MUX_MODE7 | AM33XX_PULL_DISA | AM33XX_SLEWCTRL_SLOW}, // LED8g
The same have been done in u-boot and arch specific code of linux (3.2.0) kernel. With it, during bootup, when the u-boot hands over control to kernel, some LEDs are ON while others are OFF for a second or so, before led_init() is called.
How can we control the LED behaviour during initial part of kernel initialization code,so that all LED behaviour is consistent always?
BR,
Sourav
