diff options
author | Roger Quadros <rogerq@ti.com> | 2015-06-25 10:25:50 +0300 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2015-07-08 21:51:16 -0400 |
commit | 16fc0f8ee370d2e73eb1b5532f511fee1ad657a7 (patch) | |
tree | bcfb9c3ca67ff4555ad846d82ad1b0f6a16c060a /drivers/dma/MCD_dmaApi.c | |
parent | a5878f193341d7f01f6df173558771593169202d (diff) | |
download | talos-obmc-uboot-16fc0f8ee370d2e73eb1b5532f511fee1ad657a7.tar.gz talos-obmc-uboot-16fc0f8ee370d2e73eb1b5532f511fee1ad657a7.zip |
ARM: beagle_x15: 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>
[trini: s/PULLUP/PULL_UP/ based on DRA7xx EVM version of this patch]
Signed-off-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'drivers/dma/MCD_dmaApi.c')
0 files changed, 0 insertions, 0 deletions