diff options
| author | Daniel González Cabanelas <dgcbueu@gmail.com> | 2021-02-26 20:49:00 +0100 |
|---|---|---|
| committer | Álvaro Fernández Rojas <noltari@gmail.com> | 2021-03-05 12:23:25 +0100 |
| commit | 5601da24a89f396c173c31252d679a9eeb9913c3 (patch) | |
| tree | b754030168686e95af3e143a4db540275777b414 /target/linux/mvebu/patches-5.4 | |
| parent | bdb18e0f84bccafe1497c418b6aaa924be2de6f8 (diff) | |
| download | upstream-5601da24a89f396c173c31252d679a9eeb9913c3.tar.gz upstream-5601da24a89f396c173c31252d679a9eeb9913c3.tar.bz2 upstream-5601da24a89f396c173c31252d679a9eeb9913c3.zip | |
kernel: b53: update the BCM5365 UID
BCM63XX internal PHYs and BCM5365 SoC internal switch are both using the
same phy_driver->phy_id, causing conflicts and unnecessary probes. E.g
the BCM63XX phy internal IRQ is lost on the first probe.
The full BCM5365 UID is 0x00406370.
Use an additional byte to mask the BCM5365 UID to avoid duplicate driver
phy_id's. This will fix the IRQ issue in internal BCM63XX PHYs and avoid
more conflicts in the future.
Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
(merge both cherry-picked commits)
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
(cherry-picked from commits cbcac4fde8 and cfa43f8119)
Diffstat (limited to 'target/linux/mvebu/patches-5.4')
0 files changed, 0 insertions, 0 deletions