diff options
Diffstat (limited to 'target/linux/brcm2708/patches-4.19/950-0148-Increase-firmware-call-buffer-size-to-48-bytes.patch')
| -rw-r--r-- | target/linux/brcm2708/patches-4.19/950-0148-Increase-firmware-call-buffer-size-to-48-bytes.patch | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/target/linux/brcm2708/patches-4.19/950-0148-Increase-firmware-call-buffer-size-to-48-bytes.patch b/target/linux/brcm2708/patches-4.19/950-0148-Increase-firmware-call-buffer-size-to-48-bytes.patch new file mode 100644 index 0000000000..49c7864cf8 --- /dev/null +++ b/target/linux/brcm2708/patches-4.19/950-0148-Increase-firmware-call-buffer-size-to-48-bytes.patch @@ -0,0 +1,28 @@ +From bee18e4688b1ac325f91dd4aee8672f6201d0a8d Mon Sep 17 00:00:00 2001 +From: James Hughes <james.hughes@raspberrypi.org> +Date: Wed, 31 Oct 2018 13:00:46 +0000 +Subject: [PATCH 148/703] Increase firmware call buffer size to 48 bytes + +An assumption was made in commit a1547e0bc that 32 bytes +would be enough data buffer size for all firmware calls. However, +the axi performance monitor driver uses a call with 44 bytes +(RPI_FIRMWARE_GET_PERIPH_REG) to get the VC registers values. + +Increase value to 48 to take this in to account. + +Signed-off-by: James Hughes <james.hughes@raspberrypi.org> +--- + drivers/firmware/raspberrypi.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/drivers/firmware/raspberrypi.c ++++ b/drivers/firmware/raspberrypi.c +@@ -22,7 +22,7 @@ + #define MBOX_DATA28(msg) ((msg) & ~0xf) + #define MBOX_CHAN_PROPERTY 8 + +-#define MAX_RPI_FW_PROP_BUF_SIZE 32 ++#define MAX_RPI_FW_PROP_BUF_SIZE 48 + + static struct platform_device *rpi_hwmon; + |