diff options
| author | Arınç ÜNAL <arinc.unal@arinc9.com> | 2024-01-22 08:35:58 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2024-01-29 18:04:12 -0800 |
| commit | 04a22bef5fc2c3123fb8e517fecb650d510c5a47 (patch) | |
| tree | 9efd94bda28b8f1b62ed3b7da52e80bf12703d5e /net/ipv4/tcp_input.c | |
| parent | 6537973f2a5dc3e83a424142366fd15a2b97199f (diff) | |
| download | linux-04a22bef5fc2c3123fb8e517fecb650d510c5a47.tar.gz linux-04a22bef5fc2c3123fb8e517fecb650d510c5a47.tar.bz2 linux-04a22bef5fc2c3123fb8e517fecb650d510c5a47.zip | |
net: dsa: mt7530: do not run mt7530_setup_port5() if port 5 is disabled
There's no need to run all the code on mt7530_setup_port5() if port 5 is
disabled. The only case for calling mt7530_setup_port5() from
mt7530_setup() is when PHY muxing is enabled. That is because port 5 is not
defined as a port on the devicetree, therefore, it cannot be controlled by
phylink.
Because of this, run mt7530_setup_port5() if priv->p5_intf_sel is
P5_INTF_SEL_PHY_P0 or P5_INTF_SEL_PHY_P4. Remove the P5_DISABLED case from
mt7530_setup_port5().
Stop initialising the interface variable as the remaining cases will always
call mt7530_setup_port5() with it initialised.
Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
Link: https://lore.kernel.org/r/20240122-for-netnext-mt7530-improvements-1-v3-7-042401f2b279@arinc9.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/ipv4/tcp_input.c')
0 files changed, 0 insertions, 0 deletions