Skip to content

Tags: Turdari/linux

Tags

1.20210805

Toggle 1.20210805's commit message
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]>

1.20210727

Toggle 1.20210727's commit message
configs: Add SND_BCM2708_SOC_CHIPDIP_DAC

Enable the driver for the ChipDip DAC soundcard.

Signed-off-by: Evgenij Sapunov <[email protected]>

raspberrypi-kernel_1.20210527-1

Toggle raspberrypi-kernel_1.20210527-1's commit message
overlays: Add rpi-poe-plus overlay

Signed-off-by: Serge Schneider <[email protected]>

raspberrypi-kernel_1.20210430-1

Toggle raspberrypi-kernel_1.20210430-1's commit message
ARM: dts: bcm2711-rpi-400: Limit MDIO clock speed

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

raspberrypi-kernel_1.20210303-1

Toggle raspberrypi-kernel_1.20210303-1's commit message
Merge remote-tracking branch 'stable/linux-5.10.y' into rpi-5.10.y

raspberrypi-kernel_1.20210201-1

Toggle raspberrypi-kernel_1.20210201-1's commit message
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 <[email protected]>

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

raspberrypi-kernel_1.20210111.master-1

Toggle raspberrypi-kernel_1.20210111.master-1's commit message
bcm2835-dma: Squash: Move DMA_WIDE flags to 24,25 to avoid conflict

Signed-off-by: popcornmix <[email protected]>

raspberrypi-kernel_1.20210108.master-1

Toggle raspberrypi-kernel_1.20210108.master-1's commit message
bcm2711-rpi.dtsi: Bump hdmi audio dma priority to max

Set panic priority to 15 and leave normal priority at 0

Signed-off-by: Dom Cobley <[email protected]>

raspberrypi-kernel_1.20210107.master-1

Toggle raspberrypi-kernel_1.20210107.master-1's commit message
staging/mmal-vchiq: Fix incorrect static vchiq_instance.

For some reason lost in history function vchiq_mmal_init used
a static variable for storing the vchiq_instance.
This value is retrieved from vchiq per instance, so worked fine
until you try to call vchiq_mmal_init multiple times concurrently
when things then go wrong. This seemed to happen quite frequently
if using the cutdown firmware (no MMAL or VCSM services running)
as the vchiq_connect then failed, and one or other vchiq_shutdown
was working on an invalid handle.

Remove the static so that each caller gets a unique vchiq_instance.

Signed-off-by: Dave Stevenson <[email protected]>

raspberrypi-kernel_1.20210108-1

Toggle raspberrypi-kernel_1.20210108-1's commit message
Merge remote-tracking branch 'stable/linux-5.4.y' into rpi-5.4.y