From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Sergey Suloev <ssuloev@orpaltech.com>,
linux-rpi-kernel@lists.infradead.org
Cc: "Stefan Wahren" <stefan.wahren@i2se.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: vc4 on rpi3 A+
Date: Thu, 20 Feb 2020 10:25:46 +0100 [thread overview]
Message-ID: <4850fa1006d5a329c2e6d4e61ec6fb9420125414.camel@suse.de> (raw)
In-Reply-To: <8b353626-f62a-2aff-96b4-91712ed36095@orpaltech.com>
[-- 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
next prev parent reply other threads:[~2020-02-20 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 8:21 vc4 on rpi3 A+ Sergey Suloev
2020-02-20 9:25 ` Nicolas Saenz Julienne [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4850fa1006d5a329c2e6d4e61ec6fb9420125414.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=noralf@tronnes.org \
--cc=ssuloev@orpaltech.com \
--cc=stefan.wahren@i2se.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.