lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 3 Jun 2020 22:11:26 +0200 From: Stefan Wahren <stefan.wahren@...e.com> To: Maxime Ripard <maxime@...no.tech>, Nicolas Saenz Julienne <nsaenzjulienne@...e.de>, Eric Anholt <eric@...olt.net> Cc: Tim Gover <tim.gover@...pberrypi.com>, Dave Stevenson <dave.stevenson@...pberrypi.com>, linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org, bcm-kernel-feedback-list@...adcom.com, linux-rpi-kernel@...ts.infradead.org, Phil Elwell <phil@...pberrypi.com>, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH v3 105/105] ARM: dts: bcm2711: Enable the display pipeline Hi Maxime, Am 27.05.20 um 17:49 schrieb Maxime Ripard: > Now that all the drivers have been adjusted for it, let's bring in the > necessary device tree changes. > > Signed-off-by: Maxime Ripard <maxime@...no.tech> > --- > arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 46 +++++++++++- > arch/arm/boot/dts/bcm2711.dtsi | 115 ++++++++++++++++++++++++++- > 2 files changed, 160 insertions(+), 1 deletion(-) > > diff --git a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts > index 222d7825e1ab..c4a650ea4e21 100644 > --- a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts > +++ b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts > @@ -231,3 +231,49 @@ > &vchiq { > interrupts = <GIC_SPI 34 IRQ_TYPE_LEVEL_HIGH>; > }; > + > +&vc4 { > + status = "okay"; > +}; > + > +&pixelvalve0 { > + status = "okay"; > +}; > + > +&pixelvalve1 { > + status = "okay"; > +}; > + > +&pixelvalve2 { > + status = "okay"; > +}; > + > +&pixelvalve4 { > + status = "okay"; > +}; > + > +&vec { > + status = "disabled"; > +}; > + > +&hdmi0 { > + clocks = <&firmware_clocks 13>, <&dvp 0>; > + status = "okay"; > +}; > + > +&ddc0 { > + status = "okay"; > +}; > + > +&hdmi1 { > + clocks = <&firmware_clocks 13>, <&dvp 1>; > + status = "okay"; > +}; > + > +&ddc1 { > + status = "okay"; > +}; > + > +&hvs { > + clocks = <&firmware_clocks 4>; > +}; it would be nice to have these references in alphabetical order. Regards
Powered by blists - more mailing lists