From: Sergey Suloev <ssuloev@orpaltech.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-rpi-kernel@lists.infradead.org,
Stefan Wahren <wahrenst@gmx.net>
Cc: "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: Sat, 29 Feb 2020 18:23:36 +0300 [thread overview]
Message-ID: <3ca12680-4843-4fb2-3145-0152edca96d1@orpaltech.com> (raw)
In-Reply-To: <b71f1af17d68ee66a2781a694e8a77dcafedd76b.camel@suse.de>
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
prev parent reply other threads:[~2020-02-29 15:23 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
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 message]
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=3ca12680-4843-4fb2-3145-0152edca96d1@orpaltech.com \
--to=ssuloev@orpaltech.com \
--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=nsaenzjulienne@suse.de \
--cc=wahrenst@gmx.net \
/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.