linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* vc4 on rpi3 A+
@ 2020-02-20  8:21 Sergey Suloev
  2020-02-20  9:25 ` Nicolas Saenz Julienne
  2020-02-28 13:09 ` Nicolas Saenz Julienne
  0 siblings, 2 replies; 9+ messages in thread
From: Sergey Suloev @ 2020-02-20  8:21 UTC (permalink / raw)
  To: linux-rpi-kernel
  Cc: Stefan Wahren, Noralf Trønnes, bcm-kernel-feedback-list,
	Nicolas Saenz Julienne, linux-arm-kernel

Hello, guys,

could anyone clarify the status of vc4 drm support on RPI 3A+ ?

I tried to build kernel 5.5 and 5.6-rc2 in 32bit and aarch64 
configurations with VC4 turned ON but both unsuccessful - vc4 drm driver 
is listed in memory but not working and not producing any typical DRM 
log output.


Thank you


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: vc4 on rpi3 A+
  2020-02-20  8:21 vc4 on rpi3 A+ Sergey Suloev
@ 2020-02-20  9:25 ` Nicolas Saenz Julienne
  2020-02-20  9:39   ` Sergey Suloev
  2020-02-20  9:52   ` Sergey Suloev
  2020-02-28 13:09 ` Nicolas Saenz Julienne
  1 sibling, 2 replies; 9+ messages in thread
From: Nicolas Saenz Julienne @ 2020-02-20  9:25 UTC (permalink / raw)
  To: Sergey Suloev, linux-rpi-kernel
  Cc: Stefan Wahren, Noralf Trønnes, bcm-kernel-feedback-list,
	linux-arm-kernel


[-- Attachment #1.1: Type: text/plain, Size: 2114 bytes --]

Hi Sergey,

On Thu, 2020-02-20 at 11:21 +0300, Sergey Suloev wrote:
> Hello, guys,
> 
> could anyone clarify the status of vc4 drm support on RPI 3A+ ?

I don't have one so I can't really tell for that specific board, but I'm going
to try to reproduce it on a rpi3b.

> I tried to build kernel 5.5 and 5.6-rc2 in 32bit and aarch64 
> configurations with VC4 turned ON but both unsuccessful - vc4 drm driver 
> is listed in memory but not working and not producing any typical DRM 
> log output.

AFAIK there is a known issue in 5.6-rc2, which has already been addressed[1].
Note that the driver fails on probe so there is some amount of DRM output.

I tried to reproduce your issue with v5.5, but vc4 seems to probe alright
(rpi3b+aarch64+defconfig):

	[   15.443047] vc4_hdmi 3f902000.hdmi: vc4-hdmi-hifi <-> 3f902000.hdmi mapping ok
	[   15.452864] vc4_hdmi 3f902000.hdmi: ASoC: no DMI vendor name!
	[   15.459836] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
	[   15.467062] vc4-drm soc:gpu: bound 3f806000.vec (ops vc4_vec_ops [vc4])
	[   15.478722] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4])
	[   15.485749] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
	[   15.499009] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
	[   15.526217] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
	[   15.542257] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
	[   15.560113] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
	[   15.574684] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
	[   15.587375] [drm] Driver supports precise vblank timestamp query.
	[   15.606831] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0
	[   15.617505] Console: switching to colour frame buffer device 90x30
	[   15.627858] vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device

Could it be that you forgot to update the device tree or kernel modules?

Regards,
Nicolas

[1] https://lkml.kernel.org/lkml/20200219102526.692126-1-jbrunet@baylibre.com/T/


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: vc4 on rpi3 A+
  2020-02-20  9:25 ` Nicolas Saenz Julienne
@ 2020-02-20  9:39   ` Sergey Suloev
  2020-02-24 15:02     ` Nicolas Saenz Julienne
  2020-02-20  9:52   ` Sergey Suloev
  1 sibling, 1 reply; 9+ messages in thread
From: Sergey Suloev @ 2020-02-20  9:39 UTC (permalink / raw)
  To: Nicolas Saenz Julienne, linux-rpi-kernel
  Cc: Stefan Wahren, Noralf Trønnes, bcm-kernel-feedback-list,
	linux-arm-kernel

Ni, Nicolas,

On 2/20/20 12:25 PM, Nicolas Saenz Julienne wrote:
> Hi Sergey,
>
> On Thu, 2020-02-20 at 11:21 +0300, Sergey Suloev wrote:
>> Hello, guys,
>>
>> could anyone clarify the status of vc4 drm support on RPI 3A+ ?
> I don't have one so I can't really tell for that specific board, but I'm going
> to try to reproduce it on a rpi3b.
>
>> I tried to build kernel 5.5 and 5.6-rc2 in 32bit and aarch64
>> configurations with VC4 turned ON but both unsuccessful - vc4 drm driver
>> is listed in memory but not working and not producing any typical DRM
>> log output.
> AFAIK there is a known issue in 5.6-rc2, which has already been addressed[1].
> Note that the driver fails on probe so there is some amount of DRM output.
>
> I tried to reproduce your issue with v5.5, but vc4 seems to probe alright
> (rpi3b+aarch64+defconfig):
>
> 	[   15.443047] vc4_hdmi 3f902000.hdmi: vc4-hdmi-hifi <-> 3f902000.hdmi mapping ok
> 	[   15.452864] vc4_hdmi 3f902000.hdmi: ASoC: no DMI vendor name!
> 	[   15.459836] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
> 	[   15.467062] vc4-drm soc:gpu: bound 3f806000.vec (ops vc4_vec_ops [vc4])
> 	[   15.478722] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4])
> 	[   15.485749] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
> 	[   15.499009] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
> 	[   15.526217] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
> 	[   15.542257] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
> 	[   15.560113] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
> 	[   15.574684] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> 	[   15.587375] [drm] Driver supports precise vblank timestamp query.
> 	[   15.606831] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0
> 	[   15.617505] Console: switching to colour frame buffer device 90x30
> 	[   15.627858] vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device
>
> Could it be that you forgot to update the device tree or kernel modules?
>
> Regards,
> Nicolas
>
> [1] https://lkml.kernel.org/lkml/20200219102526.692126-1-jbrunet@baylibre.com/T/
>

thanks for reply.

It works fine with Rpi3B, I agree with you. The issue happens with RPi 
3A+ only.


Thank you


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: vc4 on rpi3 A+
  2020-02-20  9:25 ` Nicolas Saenz Julienne
  2020-02-20  9:39   ` Sergey Suloev
@ 2020-02-20  9:52   ` Sergey Suloev
  1 sibling, 0 replies; 9+ messages in thread
From: Sergey Suloev @ 2020-02-20  9:52 UTC (permalink / raw)
  To: Nicolas Saenz Julienne, linux-rpi-kernel
  Cc: Stefan Wahren, Noralf Trønnes, bcm-kernel-feedback-list,
	linux-arm-kernel

Hi, Nicolas,

On 2/20/20 12:25 PM, Nicolas Saenz Julienne wrote:
> Hi Sergey,
>
> On Thu, 2020-02-20 at 11:21 +0300, Sergey Suloev wrote:
>> Hello, guys,
>>
>> could anyone clarify the status of vc4 drm support on RPI 3A+ ?
> I don't have one so I can't really tell for that specific board, but I'm going
> to try to reproduce it on a rpi3b.
>
>> I tried to build kernel 5.5 and 5.6-rc2 in 32bit and aarch64
>> configurations with VC4 turned ON but both unsuccessful - vc4 drm driver
>> is listed in memory but not working and not producing any typical DRM
>> log output.
> AFAIK there is a known issue in 5.6-rc2, which has already been addressed[1].
> Note that the driver fails on probe so there is some amount of DRM output.
>
> I tried to reproduce your issue with v5.5, but vc4 seems to probe alright
> (rpi3b+aarch64+defconfig):
>
> 	[   15.443047] vc4_hdmi 3f902000.hdmi: vc4-hdmi-hifi <-> 3f902000.hdmi mapping ok
> 	[   15.452864] vc4_hdmi 3f902000.hdmi: ASoC: no DMI vendor name!
> 	[   15.459836] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
> 	[   15.467062] vc4-drm soc:gpu: bound 3f806000.vec (ops vc4_vec_ops [vc4])
> 	[   15.478722] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4])
> 	[   15.485749] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
> 	[   15.499009] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
> 	[   15.526217] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
> 	[   15.542257] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
> 	[   15.560113] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
> 	[   15.574684] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> 	[   15.587375] [drm] Driver supports precise vblank timestamp query.
> 	[   15.606831] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0
> 	[   15.617505] Console: switching to colour frame buffer device 90x30
> 	[   15.627858] vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device
>
> Could it be that you forgot to update the device tree or kernel modules?
>
> Regards,
> Nicolas
>
> [1] https://lkml.kernel.org/lkml/20200219102526.692126-1-jbrunet@baylibre.com/T/
>

the patch [1] has already been included into 5.6-rc2, so the issue with 
Rpi 3A+ isn't related to that.

[1] 
https://lkml.kernel.org/lkml/20200219102526.692126-1-jbrunet@baylibre.com/T/


Thank you


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: vc4 on rpi3 A+
  2020-02-20  9:39   ` Sergey Suloev
@ 2020-02-24 15:02     ` Nicolas Saenz Julienne
  0 siblings, 0 replies; 9+ messages in thread
From: Nicolas Saenz Julienne @ 2020-02-24 15:02 UTC (permalink / raw)
  To: Sergey Suloev, linux-rpi-kernel
  Cc: Stefan Wahren, Noralf Trønnes, bcm-kernel-feedback-list,
	linux-arm-kernel


[-- Attachment #1.1: Type: text/plain, Size: 2801 bytes --]

On Thu, 2020-02-20 at 12:39 +0300, Sergey Suloev wrote:
> Ni, Nicolas,
> 
> On 2/20/20 12:25 PM, Nicolas Saenz Julienne wrote:
> > Hi Sergey,
> > 
> > On Thu, 2020-02-20 at 11:21 +0300, Sergey Suloev wrote:
> > > Hello, guys,
> > > 
> > > could anyone clarify the status of vc4 drm support on RPI 3A+ ?
> > I don't have one so I can't really tell for that specific board, but I'm
> > going
> > to try to reproduce it on a rpi3b.
> > 
> > > I tried to build kernel 5.5 and 5.6-rc2 in 32bit and aarch64
> > > configurations with VC4 turned ON but both unsuccessful - vc4 drm driver
> > > is listed in memory but not working and not producing any typical DRM
> > > log output.
> > AFAIK there is a known issue in 5.6-rc2, which has already been
> > addressed[1].
> > Note that the driver fails on probe so there is some amount of DRM output.
> > 
> > I tried to reproduce your issue with v5.5, but vc4 seems to probe alright
> > (rpi3b+aarch64+defconfig):
> > 
> > 	[   15.443047] vc4_hdmi 3f902000.hdmi: vc4-hdmi-hifi <-> 3f902000.hdmi
> > mapping ok
> > 	[   15.452864] vc4_hdmi 3f902000.hdmi: ASoC: no DMI vendor name!
> > 	[   15.459836] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops
> > [vc4])
> > 	[   15.467062] vc4-drm soc:gpu: bound 3f806000.vec (ops vc4_vec_ops
> > [vc4])
> > 	[   15.478722] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops
> > [vc4])
> > 	[   15.485749] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops
> > [vc4])
> > 	[   15.499009] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops
> > vc4_crtc_ops [vc4])
> > 	[   15.526217] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops
> > vc4_crtc_ops [vc4])
> > 	[   15.542257] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops
> > vc4_crtc_ops [vc4])
> > 	[   15.560113] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops
> > [vc4])
> > 	[   15.574684] [drm] Supports vblank timestamp caching Rev 2
> > (21.10.2013).
> > 	[   15.587375] [drm] Driver supports precise vblank timestamp query.
> > 	[   15.606831] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor
> > 0
> > 	[   15.617505] Console: switching to colour frame buffer device 90x30
> > 	[   15.627858] vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device
> > 
> > Could it be that you forgot to update the device tree or kernel modules?
> > 
> > Regards,
> > Nicolas
> > 
> > [1] 
> > https://lkml.kernel.org/lkml/20200219102526.692126-1-jbrunet@baylibre.com/T/
> > 
> 
> thanks for reply.
> 
> It works fine with Rpi3B, I agree with you. The issue happens with RPi 
> 3A+ only.

I'll soon have access to a rpi3a+ and look deeper into it.

Meanwhile, if you have the time, I'd suggest adding prints to the vc4 driver
code to find out where it's going wrong.

Regards,
Nicolas


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: vc4 on rpi3 A+
  2020-02-20  8:21 vc4 on rpi3 A+ Sergey Suloev
  2020-02-20  9:25 ` Nicolas Saenz Julienne
@ 2020-02-28 13:09 ` Nicolas Saenz Julienne
  2020-02-28 16:22   ` Stefan Wahren
                     ` (2 more replies)
  1 sibling, 3 replies; 9+ messages in thread
From: Nicolas Saenz Julienne @ 2020-02-28 13:09 UTC (permalink / raw)
  To: Sergey Suloev, linux-rpi-kernel, Stefan Wahren
  Cc: Noralf Trønnes, bcm-kernel-feedback-list, linux-arm-kernel


[-- Attachment #1.1.1: Type: text/plain, Size: 827 bytes --]

Hi Sergey,

On Thu, 2020-02-20 at 11:21 +0300, Sergey Suloev wrote:
> Hello, guys,
> 
> could anyone clarify the status of vc4 drm support on RPI 3A+ ?
> 
> I tried to build kernel 5.5 and 5.6-rc2 in 32bit and aarch64 
> configurations with VC4 turned ON but both unsuccessful - vc4 drm driver 
> is listed in memory but not working and not producing any typical DRM 
> log output.

I managed to get my hands on a rpi3a+ and reproduce the issue. 'dmesg -lerr'
outputs this:

	bcm2835-power: Timeout waiting for grafx power OK

This is a known issue, see https://github.com/raspberrypi/linux/issues/3046.
I attached a device-tree patch in case you want to verify it fixes the issue on
your board.

@Stefan I guess I'm going to have to revert the pm patch, any comments before I
do?

Regards,
Nicolas


[-- Attachment #1.1.2: 0001-HACK-ARM-dts-Use-v3d-s-firmware-based-power-domain-o.patch --]
[-- Type: text/x-patch, Size: 1308 bytes --]

From e6d1aaab89af656fbb69845ce8ea8753059894a3 Mon Sep 17 00:00:00 2001
From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Date: Fri, 28 Feb 2020 14:03:22 +0100
Subject: [PATCH] HACK: ARM: dts: Use v3d's firmware based power domain on
 rpi3a+

temp fix...

Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
---
 arch/arm/boot/dts/bcm2835-common.dtsi      | 1 -
 arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts | 4 ++++
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/bcm2835-common.dtsi b/arch/arm/boot/dts/bcm2835-common.dtsi
index 2b1d9d4c0cde..4119271c979d 100644
--- a/arch/arm/boot/dts/bcm2835-common.dtsi
+++ b/arch/arm/boot/dts/bcm2835-common.dtsi
@@ -130,7 +130,6 @@ v3d: v3d@7ec00000 {
 			compatible = "brcm,bcm2835-v3d";
 			reg = <0x7ec00000 0x1000>;
 			interrupts = <1 10>;
-			power-domains = <&pm BCM2835_POWER_DOMAIN_GRAFX_V3D>;
 		};
 
 		vc4: gpu {
diff --git a/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts b/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts
index 66ab35eccba7..7fddede92b68 100644
--- a/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts
+++ b/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts
@@ -176,3 +176,7 @@ &uart1 {
 	pinctrl-0 = <&uart1_gpio14>;
 	status = "okay";
 };
+
+&v3d {
+	power-domains = <&power RPI_POWER_DOMAIN_V3D>;
+};
-- 
2.25.1


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply related	[flat|nested] 9+ messages in thread
* Re: vc4 on rpi3 A+
  2020-02-28 13:09 ` Nicolas Saenz Julienne
@ 2020-02-28 16:22   ` Stefan Wahren
  2020-02-29 12:07   ` Stefan Wahren
  2020-02-29 15:23   ` Sergey Suloev
  2 siblings, 0 replies; 9+ messages in thread
From: Stefan Wahren @ 2020-02-28 16:22 UTC (permalink / raw)
  To: Nicolas Saenz Julienne, Sergey Suloev, linux-rpi-kernel, Stefan Wahren
  Cc: Noralf Trønnes, bcm-kernel-feedback-list, linux-arm-kernel

Hi Nicolas,

Am 28.02.20 um 14:09 schrieb Nicolas Saenz Julienne:
> Hi Sergey,
>
> On Thu, 2020-02-20 at 11:21 +0300, Sergey Suloev wrote:
>> Hello, guys,
>>
>> could anyone clarify the status of vc4 drm support on RPI 3A+ ?
>>
>> I tried to build kernel 5.5 and 5.6-rc2 in 32bit and aarch64 
>> configurations with VC4 turned ON but both unsuccessful - vc4 drm driver 
>> is listed in memory but not working and not producing any typical DRM 
>> log output.
> I managed to get my hands on a rpi3a+ and reproduce the issue. 'dmesg -lerr'
> outputs this:
>
> 	bcm2835-power: Timeout waiting for grafx power OK
>
> This is a known issue, see https://github.com/raspberrypi/linux/issues/3046.
> I attached a device-tree patch in case you want to verify it fixes the issue on
> your board.
>
> @Stefan I guess I'm going to have to revert the pm patch, any comments before I
> do?

last time i try to revert the pm patch causes reliable hang of Raspbian.

I will try to test it again.

Regards
Stefan

>
> Regards,
> Nicolas
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: vc4 on rpi3 A+
  2020-02-28 13:09 ` Nicolas Saenz Julienne
  2020-02-28 16:22   ` Stefan Wahren
@ 2020-02-29 12:07   ` Stefan Wahren
  2020-02-29 15:23   ` Sergey Suloev
  2 siblings, 0 replies; 9+ messages in thread
From: Stefan Wahren @ 2020-02-29 12:07 UTC (permalink / raw)
  To: Nicolas Saenz Julienne, Sergey Suloev, linux-rpi-kernel, Stefan Wahren
  Cc: Noralf Trønnes, bcm-kernel-feedback-list, Maxime Ripard,
	linux-arm-kernel

Hi Nicolas,

Am 28.02.20 um 14:09 schrieb Nicolas Saenz Julienne:
> Hi Sergey,
>
> On Thu, 2020-02-20 at 11:21 +0300, Sergey Suloev wrote:
>> Hello, guys,
>>
>> could anyone clarify the status of vc4 drm support on RPI 3A+ ?
>>
>> I tried to build kernel 5.5 and 5.6-rc2 in 32bit and aarch64 
>> configurations with VC4 turned ON but both unsuccessful - vc4 drm driver 
>> is listed in memory but not working and not producing any typical DRM 
>> log output.
> I managed to get my hands on a rpi3a+ and reproduce the issue. 'dmesg -lerr'
> outputs this:
>
> 	bcm2835-power: Timeout waiting for grafx power OK
>
> This is a known issue, see https://github.com/raspberrypi/linux/issues/3046.
> I attached a device-tree patch in case you want to verify it fixes the issue on
> your board.

i tested recent linux-next (multi_v7_defconfig) on my Raspberry Pi 3A+
with current Raspbian.

Without your patch the LXDE does come up, but i also see those timeouts
and the v3d part hangs in a deferrred probe.

With your patch the LXDE doesn't come up.

Unfortunately i don't have any newer suggestions other the mentioned in
the github issue.

Best regards
Stefan

>
> @Stefan I guess I'm going to have to revert the pm patch, any comments before I
> do?
>
> Regards,
> Nicolas
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: vc4 on rpi3 A+
  2020-02-28 13:09 ` Nicolas Saenz Julienne
  2020-02-28 16:22   ` Stefan Wahren
  2020-02-29 12:07   ` Stefan Wahren
@ 2020-02-29 15:23   ` Sergey Suloev
  2 siblings, 0 replies; 9+ messages in thread
From: Sergey Suloev @ 2020-02-29 15:23 UTC (permalink / raw)
  To: Nicolas Saenz Julienne, linux-rpi-kernel, Stefan Wahren
  Cc: Noralf Trønnes, bcm-kernel-feedback-list, linux-arm-kernel

Hi, Nicolas,

On 2/28/20 4:09 PM, Nicolas Saenz Julienne wrote:
> Hi Sergey,
>
> On Thu, 2020-02-20 at 11:21 +0300, Sergey Suloev wrote:
>> Hello, guys,
>>
>> could anyone clarify the status of vc4 drm support on RPI 3A+ ?
>>
>> I tried to build kernel 5.5 and 5.6-rc2 in 32bit and aarch64
>> configurations with VC4 turned ON but both unsuccessful - vc4 drm driver
>> is listed in memory but not working and not producing any typical DRM
>> log output.
> I managed to get my hands on a rpi3a+ and reproduce the issue. 'dmesg -lerr'
> outputs this:
>
> 	bcm2835-power: Timeout waiting for grafx power OK
>
> This is a known issue, see https://github.com/raspberrypi/linux/issues/3046.
> I attached a device-tree patch in case you want to verify it fixes the issue on
> your board.

the patch works, thank you


> @Stefan I guess I'm going to have to revert the pm patch, any comments before I
> do?
>
> Regards,
> Nicolas
>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 9+ messages in thread
end of thread, other threads:[~2020-02-29 15:23 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-20  8:21 vc4 on rpi3 A+ Sergey Suloev
2020-02-20  9:25 ` Nicolas Saenz Julienne
2020-02-20  9:39   ` Sergey Suloev
2020-02-24 15:02     ` Nicolas Saenz Julienne
2020-02-20  9:52   ` Sergey Suloev
2020-02-28 13:09 ` Nicolas Saenz Julienne
2020-02-28 16:22   ` Stefan Wahren
2020-02-29 12:07   ` Stefan Wahren
2020-02-29 15:23   ` Sergey Suloev

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).