summaryrefslogtreecommitdiffstats
path: root/board/ti/beagle_x15/mux_data.h
diff options
context:
space:
mode:
authorRoger Quadros <rogerq@ti.com>2015-06-24 17:00:11 +0300
committerTom Rini <trini@konsulko.com>2015-07-08 18:26:42 -0400
commita5878f193341d7f01f6df173558771593169202d (patch)
tree08567b0f37ebd613948019f9ce1bd24c0bd05942 /board/ti/beagle_x15/mux_data.h
parent687a7518a1b1e40e005711603dcb14e0f6942d6d (diff)
downloadtalos-obmc-uboot-a5878f193341d7f01f6df173558771593169202d.tar.gz
talos-obmc-uboot-a5878f193341d7f01f6df173558771593169202d.zip
ARM: DRA7-evm: prevent DCAN1 _wait_target_disable failure in kernel
If board is booted with transitions happening on DCAN1 pins then the following warning is seen in the kernel at boot when the hwmod layer initializes. "omap_hwmod: dcan1: _wait_target_disable failed" This is because DCAN1 module's SWAKEUP mechanism is broken and it fails to correctly turn OFF if it sees a transition on the DCAN1 pins. Suggested workaround is to keep DCAN1 pins in safe mode while enabling/disabling DCAN1 module. The hwmod layer enables and disables all modules at boot and we have no opportunity to put the DCAN1 pins in safe mode at that point. DCAN1 is not used by u-boot so it doesn't matter to it if these pins are in safe mode. The kernel driver correctly configures the right mode when DCAN1 is active. Signed-off-by: Roger Quadros <rogerq@ti.com>
Diffstat (limited to 'board/ti/beagle_x15/mux_data.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud