From: Heiner Kallweit <hkallweit1@gmail.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: "open list:ARM/Amlogic Meson..." <linux-amlogic@lists.infradead.org>
Subject: Re: Solid green screen with experimental panfrost/hdmi sc2 support
Date: Wed, 27 Apr 2022 11:37:22 +0200 [thread overview]
Message-ID: <04527367-b26f-d843-7711-d75c543b5787@gmail.com> (raw)
In-Reply-To: <a8b8d5e8-758a-3cf5-6798-6769021ec4b4@baylibre.com>
On 26.04.2022 09:28, Neil Armstrong wrote:
> Hi,
>
> On 25/04/2022 22:21, Heiner Kallweit wrote:
>> Based on a HK1 RBOX X4 (S905X4) I'm "playing" with mainline support for SC2.
>> This Android TV box is based on the ah212 reference board according to uboot prompt.
>> Most relevant things are working meanwhile (eMMC, SD, SDIO/WiFi, USB2/3, ethernet)
>> and I can use the system headless.
>> However I'm struggling with panfrost/hdmi. With SC2 a lot of vpu registers have been
>> relocated (e.g. all hhi regs), even though the functionality seems to be more or less
>> compatible to G12A. I had to extend the timeout for HDMI PLL locking.
>> After having sorted out such things:
>> - dmesg for panfrost and hdmi looks normal
>> - monitor detects signal and OSD shows correct resolution (1920x1080@60 in my case).
>> I'd interpret this in a way that the clock/divider/mux registers are programmed correctly.
>> However I just get a solid green screen. From what I've read this can be caused
>> by a failing hdmi handshake. Not being an expert in DRM/HDMI any hint on where to start
>> debugging would be appreciated.
>
> A solid green means the pipeline has been correctly set up in regard to the clocking,
> and some (invalid) pixels flows to the HDMI transceiver.
>
> This means you can consider the HDMI & clock portion OK, and propably the ENCP aswell.
>
> The OSD video pipeline is the following:
>
> [ DDR -> VIU (RGB2YUV) -> VPP (Blending of planes, Scaling) -> ENCP (Pixel generation) -> HDMI-TX -> TMDS]
>
> Green means value 0 in YUV, this means 0 is in the YUV pipeline, so it must be an issue with the VIU
> part reading from DDR and doing the color conversion.
>
> Check in the downstrean source code how the SC2 VPU is initialized, and looks at the differences since SM1.
> Look at the VIU & VPP stuff init.
>
I found that in case of the solid green screen the number of crtc interrupts (handled by meson_crtc_irq())
is constantly increasing, with a rate of a few hundred interrupts per minute.
On a S905W-based system where HDMI output works normally I see about 100 such interrupts after boot
and the number doesn't change.
Maybe this can provide a hint on what's going wrong?
> Neil
>
Heiner
>>
>>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2022-04-27 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 20:21 Solid green screen with experimental panfrost/hdmi sc2 support Heiner Kallweit
2022-04-26 7:28 ` Neil Armstrong
2022-04-26 8:54 ` Heiner Kallweit
2022-04-27 9:37 ` Heiner Kallweit [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=04527367-b26f-d843-7711-d75c543b5787@gmail.com \
--to=hkallweit1@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.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 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).