Merge remote-tracking branch 'stable/linux-5.10.y' into rpi-5.10.y

Merge remote-tracking branch 'stable/linux-5.10.y' into rpi-5.10.y

configs: Add USB gadget support (for Zero 2 W)

Bring the Pi 3 kernel in line with the Pi Zero and Pi 4 by enabling
USB gadget support, which is useful on Zero 2 W.

See: raspberrypi/firmware#1654

Signed-off-by: Phil Elwell <[email protected]>

ARM: dts: Add Pi Zero 2 support

Signed-off-by: Phil Elwell <[email protected]>

ARM: dts: Add Pi Zero 2 support

Signed-off-by: Phil Elwell <[email protected]>

dwc_otg: pay attention to qh->interval when rescheduling periodic queues

A regression introduced in raspberrypi#3887
meant that if the newly scheduled transfer immediately returned data, and
the driver resubmitted a single URB after every transfer, then the effective
polling interval would end up being approx 1ms.

Use the larger of SCHEDULE_SLOP or the configured endpoint interval.

Signed-off-by: Jonathan Bell <[email protected]>

dwc_otg: pay attention to qh->interval when rescheduling periodic queues

A regression introduced in raspberrypi#3887
meant that if the newly scheduled transfer immediately returned data, and
the driver resubmitted a single URB after every transfer, then the effective
polling interval would end up being approx 1ms.

Use the larger of SCHEDULE_SLOP or the configured endpoint interval.

Signed-off-by: Jonathan Bell <[email protected]>

bcm2835_smi_dev: Fix handling of word-odd lengths

The read and write functions did not use the correct pointer offset
when dealing with an odd number of bytes after a DMA transfer. Also,
only handle the remaining odd bytes if the DMA transfer completed
successfully.

Submitted-by: @madimario (GitHub)
Signed-off-by: Phil Elwell <[email protected]>

drm/vc4: Set a default HSM rate

When the firmware doesn't setup the HSM rate (such as when booting
without an HDMI cable plugged in), its rate is 0 and thus any register
access results in a CPU stall, even though HSM is enabled.

Let's enforce a minimum rate at boot to avoid this issue.

Signed-off-by: Maxime Ripard <[email protected]>

overlays: Reduce Pi 4 vc4 CMA size to 320MB

Reduce the default CMA allocation requested by the vc4-kms-v3d-pi4 and
vc4-fkms-v3d-pi4 overlays to 320MB.

Use magic values of the form (<n>*64 - 4)MB to encode default values
of <n>*64MB, allowing these defaults to be distinguished from values
set explicitly by the user with the usual overlay parameters (e.g.
"cma-384"). Only default values will be capped if the Pi RAM is too
small or the gpu_mem setting too large for it to be viable.

Signed-off-by: Phil Elwell <[email protected]>