Revert "bcmgenet: constrain max DMA burst length"#7401
Conversation
This reverts commit fd2e504.
|
btw: 7dd290a looks messed up and changes genet too. rebase / merge went bad? Origin seems to be 6c7d38b Looked up the history of this commit (raspberrypi/rpi-eeprom#417) and the initial issue should be fixed in firmware with raspberrypi/rpi-eeprom#424. So given the amount of potential energy savings, this is also worth considering a revert. I will do some testing. |
|
And I agree with this reversion of a downstream patch that is no longer required. |
AFAIU it can / should be reverted too, once this is split. The firmware should be changed for quite a few years and according to Florian the power savings are worth it. I will update the pr with a split + revert so we can test. OK? |
Sure - I'll rope @P33M in for comment. |
|
In #3030 I narrowed the reproducer to Pi 4 + |
|
Seems to be a misunderstanding, I was only talking about the genet patch which was accidentaly squashed into the xhci patch. So the revert would be only for the genet part |
|
I was fooled - your talk of firmware made me think of the VL805. |
|
My bad. Firmware = bootloader firmware in spi flash (phy needed proper reset for netboot four years ago) |
|
to be continued here #7403 |
While debugging the genet issue, I spotted another redundant downstream patch.
fd2e504 dropped DMA_MAX_BURST_LENGTH from 0x10 to 0x08 back in 2018 to work around BCM2711 TX DMA timeouts. @lategoodbye's upstream a50e3a9 made this obsolete a year later by adding
bcmgenet_plat_dataand pinning 0x08 for BCM2711 only.So the global override has already been a no-op on Pi hardware for a while.