diff options
| author | Geert Uytterhoeven <geert+renesas@glider.be> | 2021-10-07 16:38:49 +0200 |
|---|---|---|
| committer | Geert Uytterhoeven <geert+renesas@glider.be> | 2021-10-15 09:48:00 +0200 |
| commit | f31a5ffbd11d9886093a6531e5a6d60e0605ce30 (patch) | |
| tree | 6a4a6e71d5cd604a15e11156f359bf3d5a73fcfa /net/ipv4/tcp_ulp.c | |
| parent | e212923e74076f423555947eff6f14355487cd21 (diff) | |
| download | linux-f31a5ffbd11d9886093a6531e5a6d60e0605ce30.tar.gz linux-f31a5ffbd11d9886093a6531e5a6d60e0605ce30.tar.bz2 linux-f31a5ffbd11d9886093a6531e5a6d60e0605ce30.zip | |
pinctrl: renesas: checker: Fix bias checks on SoCs with pull-down only pins
If some bits in a pin Pull-Up control register (PUPR) control pin
pull-down instead of pin pull-up, there are two pinmux_bias_reg entries:
a first one with the puen field filled in, listing pins with pull-up
functionality, and a second one with the pud field filled in, listing
pins with pull-down functionality. On encountering the second entry,
where puen is NULL, the for-loop terminates early, causing the remaining
bias registers not to be checked. In addition, sh_pfc_check_bias_reg()
does not handle such entries.
Fix this by treating pinmux_bias_reg.puen and pinmux_bias_reg.pud the
same.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Link: https://lore.kernel.org/r/29526d06fa223cffd785cdb264b756a202b11cea.1633615652.git.geert+renesas@glider.be
Diffstat (limited to 'net/ipv4/tcp_ulp.c')
0 files changed, 0 insertions, 0 deletions