mirror of
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2025-08-05 16:54:27 +00:00
f44fa354a0
During s2idle tests on the Raspberry CM4 the VPU firmware always crashes
on xHCI power-domain resume:
root@raspberrypi:/sys/power# echo freeze > state
[ 70.724347] xhci_suspend finished
[ 70.727730] xhci_plat_suspend finished
[ 70.755624] bcm2835-power bcm2835-power: Power grafx off
[ 70.761127] USB: Set power to 0
[ 74.653040] USB: Failed to set power to 1 (-110)
This seems to be caused because of the mixed usage of
raspberrypi-power and bcm2835-power at the same time. So avoid
the usage of the VPU firmware power-domain driver, which
prevents the VPU crash.
Fixes: 522c35e08b ("ARM: dts: bcm2711: Add BCM2711 xHCI support")
Link: https://github.com/raspberrypi/linux/issues/6537
Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
Link: https://lore.kernel.org/r/20250201112729.31509-1-wahrenst@gmx.net
Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
102 lines
1.9 KiB
Text
102 lines
1.9 KiB
Text
// SPDX-License-Identifier: GPL-2.0
|
|
#include "bcm2835-rpi.dtsi"
|
|
|
|
#include <dt-bindings/reset/raspberrypi,firmware-reset.h>
|
|
|
|
/ {
|
|
/* Will be filled by the bootloader */
|
|
memory@0 {
|
|
device_type = "memory";
|
|
reg = <0 0 0>;
|
|
};
|
|
|
|
aliases {
|
|
emmc2bus = &emmc2bus;
|
|
ethernet0 = &genet;
|
|
pcie0 = &pcie0;
|
|
blconfig = &blconfig;
|
|
};
|
|
|
|
i2c0mux: i2c-mux0 {
|
|
compatible = "i2c-mux-pinctrl";
|
|
#address-cells = <1>;
|
|
#size-cells = <0>;
|
|
|
|
i2c-parent = <&i2c0>;
|
|
|
|
pinctrl-names = "i2c0", "i2c0-vc";
|
|
pinctrl-0 = <&i2c0_gpio0>;
|
|
pinctrl-1 = <&i2c0_gpio44>;
|
|
|
|
i2c0_0: i2c@0 {
|
|
reg = <0>;
|
|
#address-cells = <1>;
|
|
#size-cells = <0>;
|
|
};
|
|
|
|
i2c0_1: i2c@1 {
|
|
reg = <1>;
|
|
#address-cells = <1>;
|
|
#size-cells = <0>;
|
|
};
|
|
};
|
|
};
|
|
|
|
&firmware {
|
|
expgpio: gpio {
|
|
compatible = "raspberrypi,firmware-gpio";
|
|
gpio-controller;
|
|
#gpio-cells = <2>;
|
|
status = "okay";
|
|
};
|
|
|
|
reset: reset {
|
|
compatible = "raspberrypi,firmware-reset";
|
|
#reset-cells = <1>;
|
|
};
|
|
};
|
|
|
|
&hdmi0 {
|
|
clocks = <&firmware_clocks 13>, <&firmware_clocks 14>, <&dvp 0>, <&clk_27MHz>;
|
|
clock-names = "hdmi", "bvb", "audio", "cec";
|
|
wifi-2.4ghz-coexistence;
|
|
};
|
|
|
|
&hdmi1 {
|
|
clocks = <&firmware_clocks 13>, <&firmware_clocks 14>, <&dvp 1>, <&clk_27MHz>;
|
|
clock-names = "hdmi", "bvb", "audio", "cec";
|
|
wifi-2.4ghz-coexistence;
|
|
};
|
|
|
|
&hvs {
|
|
clocks = <&firmware_clocks 4>;
|
|
};
|
|
|
|
&i2c0 {
|
|
/delete-property/ pinctrl-names;
|
|
/delete-property/ pinctrl-0;
|
|
};
|
|
|
|
&rmem {
|
|
/*
|
|
* RPi4's co-processor will copy the board's bootloader configuration
|
|
* into memory for the OS to consume. It'll also update this node with
|
|
* its placement information.
|
|
*/
|
|
blconfig: nvram@0 {
|
|
compatible = "raspberrypi,bootloader-config", "nvmem-rmem";
|
|
#address-cells = <1>;
|
|
#size-cells = <1>;
|
|
reg = <0x0 0x0 0x0>;
|
|
no-map;
|
|
status = "disabled";
|
|
};
|
|
};
|
|
|
|
&v3d {
|
|
clocks = <&firmware_clocks 5>;
|
|
};
|
|
|
|
&vchiq {
|
|
interrupts = <GIC_SPI 34 IRQ_TYPE_LEVEL_HIGH>;
|
|
};
|