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 <jonathan@raspberrypi.com>

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 <phil@raspberrypi.com>

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 <maxime@cerno.tech>

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 <phil@raspberrypi.com>

configs: Add SND_BCM2708_SOC_CHIPDIP_DAC

Enable the driver for the ChipDip DAC soundcard.

Signed-off-by: Evgenij Sapunov <evgenij.sapunov@chipdip.ru>

overlays: Add rpi-poe-plus overlay

Signed-off-by: Serge Schneider <serge@raspberrypi.com>

ARM: dts: bcm2711-rpi-400: Limit MDIO clock speed

Signed-off-by: Phil Elwell <phil@raspberrypi.com>

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

spi: bcm2835: Workaround/fix for zero-length transfers

A relatively recent commit ([1]) contained optimisation for the PIO
SPI FIFO-filling functions. The commit message includes the phrase
"[t]he blind and counted loops are always called with nonzero count".
This is technically true, but it is still possible for count to become
zero before the loop is entered - if tfr->len is zero. Moving the loop
exit condition to the end of the loop saves a few cycles, but results
in a near-infinite loop should the revised count be zero on entry.

Strangely, zero-lengthed transfers aren't filtered by the SPI framework
and, even more strangely, the Python3 spidev library is triggering them
for no obvious reason.

Avoid the problem completely by bailing out of the main transfer
function early if trf->len is zero, although there may be a case for
moving the mitigation into the framework.

See: raspberrypi#4100

Signed-off-by: Phil Elwell <phil@raspberrypi.com>

[1] 26751de ("spi: bcm2835: Micro-optimise FIFO loops")

bcm2835-dma: Squash: Move DMA_WIDE flags to 24,25 to avoid conflict

Signed-off-by: popcornmix <popcornmix@gmail.com>