summaryrefslogtreecommitdiffstats
path: root/include/keys
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2023-01-20 12:09:32 +0100
committerJakub Kicinski <kuba@kernel.org>2023-01-23 21:40:54 -0800
commit360fdc999d92db4a4adbba0db8641396dc9f1b13 (patch)
tree3cebd9b9de5bc4d09751975c1831a752b444776a /include/keys
parent5e9398a26a92fc402d82ce1f97cc67d832527da0 (diff)
downloadlinux-stable-360fdc999d92db4a4adbba0db8641396dc9f1b13.tar.gz
linux-stable-360fdc999d92db4a4adbba0db8641396dc9f1b13.tar.bz2
linux-stable-360fdc999d92db4a4adbba0db8641396dc9f1b13.zip
net: dsa: microchip: fix probe of I2C-connected KSZ8563
Starting with commit eee16b147121 ("net: dsa: microchip: perform the compatibility check for dev probed"), the KSZ switch driver now bails out if it thinks the DT compatible doesn't match the actual chip ID read back from the hardware: ksz9477-switch 1-005f: Device tree specifies chip KSZ9893 but found KSZ8563, please fix it! For the KSZ8563, which used ksz_switch_chips[KSZ9893], this was fine at first, because it indeed shares the same chip id as the KSZ9893. Commit b44908095612 ("net: dsa: microchip: add separate struct ksz_chip_data for KSZ8563 chip") started differentiating KSZ9893 compatible chips by consulting the 0x1F register. The resulting breakage was fixed for the SPI driver in the same commit by introducing the appropriate ksz_switch_chips[KSZ8563], but not for the I2C driver. Fix this for I2C-connected KSZ8563 now to get it probing again. Fixes: b44908095612 ("net: dsa: microchip: add separate struct ksz_chip_data for KSZ8563 chip"). Reviewed-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Acked-by: Arun Ramadoss <arun.ramadoss@microchip.com> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com> Link: https://lore.kernel.org/r/20230120110933.1151054-1-a.fatoum@pengutronix.de Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/keys')
0 files changed, 0 insertions, 0 deletions