mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-01 17:10:11 +00:00
tegra2: Fix conflicting pinmux for UARTA
Tegra appears to boot with function UARTA pre-selected on mux group SDB. If two mux groups are both set to the same function, it's unclear which group's pins drive the RX signals into the HW module. For UARTA, SDB certainly overrides group IRTX in practice. To solve this, configure some alternative function on SDB to avoid the conflict. Also, tri-state the group to avoid driving any signal onto it until we know what's connected. Signed-off-by: Stephen Warren <swarren@nvidia.com> Acked-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Warren <twarren@nvidia.com>
This commit is contained in:
parent
9cbfee6dc2
commit
4850ab9a4f
1 changed files with 12 additions and 0 deletions
|
@ -37,6 +37,18 @@ int funcmux_select(enum periph_id id, int config)
|
|||
pinmux_set_func(PINGRP_IRTX, PMUX_FUNC_UARTA);
|
||||
pinmux_tristate_disable(PINGRP_IRRX);
|
||||
pinmux_tristate_disable(PINGRP_IRTX);
|
||||
/*
|
||||
* Tegra appears to boot with function UARTA pre-selected on
|
||||
* mux group SDB. If two mux groups are both set to the same
|
||||
* function, it's unclear which group's pins drive the RX
|
||||
* signals into the HW module. For UARTA, SDB certainly
|
||||
* overrides group IRTX in practice. To solve this, configure
|
||||
* some alternative function on SDB to avoid the conflict. Also,
|
||||
* tri-state the group to avoid driving any signal onto it until
|
||||
* we know what's connected.
|
||||
*/
|
||||
pinmux_tristate_enable(PINGRP_SDB);
|
||||
pinmux_set_func(PINGRP_SDB, PMUX_FUNC_SDIO3);
|
||||
break;
|
||||
|
||||
case PERIPH_ID_UART2:
|
||||
|
|
Loading…
Reference in a new issue