On Sun, 10 Apr 2022 00:13:34 -0500
Samuel Holland wrote:
> Now that the pinmux conflict is handled in the board code (by skipping
> setup for the one conflicting MMC controller), the driver does not need
> to be entirely disabled based on the UART pinmux.
>
> Signed-off-by: Samuel Holland
Appl
On 2022/4/10 13:13, Samuel Holland wrote:
Now that the pinmux conflict is handled in the board code (by skipping
setup for the one conflicting MMC controller), the driver does not need
to be entirely disabled based on the UART pinmux.
Signed-off-by: Samuel Holland
Reviewed-by: Peng Fan
Now that the pinmux conflict is handled in the board code (by skipping
setup for the one conflicting MMC controller), the driver does not need
to be entirely disabled based on the UART pinmux.
Signed-off-by: Samuel Holland
---
drivers/mmc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deleti
3 matches
Mail list logo