mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-12 04:46:58 +07:00
6571534b60
To configure pads during the initialisation a set of special constants is used, e.g. #define MX25_PAD_FEC_MDIO__FEC_MDIO IOMUX_PAD(0x3c4, 0x1cc, 0x10, 0, 0, PAD_CTL_HYS | PAD_CTL_PUS_22K_UP) The problem is that no pull-up/down is getting activated unless both PAD_CTL_PUE (pull-up enable) and PAD_CTL_PKE (pull/keeper module enable) set. This is clearly stated in the i.MX25 datasheet and is confirmed by the measurements on hardware. This leads to some rather hard to understand bugs such as misdetecting an absent ethernet PHY (a real bug i had), unstable data transfer etc. This might affect mx25, mx35, mx50, mx51 and mx53 SoCs. It's reasonable to expect that if the pullup value is specified, the intention was to have it actually active, so we implicitly add the needed bits. Cc: stable@kernel.org Signed-off-by: Paul Fertser <fercerpav@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> |
||
|---|---|---|
| .. | ||
| devices | ||
| include/mach | ||
| 3ds_debugboard.c | ||
| audmux-v1.c | ||
| audmux-v2.c | ||
| avic.c | ||
| clock.c | ||
| cpu.c | ||
| cpufreq.c | ||
| devices.c | ||
| epit.c | ||
| iomux-v1.c | ||
| iomux-v3.c | ||
| iram_alloc.c | ||
| irq-common.c | ||
| irq-common.h | ||
| Kconfig | ||
| Makefile | ||
| pwm.c | ||
| ssi-fiq-ksym.c | ||
| ssi-fiq.S | ||
| system.c | ||
| time.c | ||
| tzic.c | ||
| ulpi.c | ||