From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [BUG] DM_VIDEO broken on imx6q
Date: Mon, 3 Aug 2020 15:54:24 +0200 [thread overview]
Message-ID: <20200803155424.78c67ad0@crub> (raw)
In-Reply-To: <6d195fc9-2342-da9c-3bb1-224ccb754861@web.de>
Hi,
On Sat, 1 Aug 2020 21:14:10 +0200
Soeren Moch smoch at web.de wrote:
> Hi,
>
> unfortunately the patch [1] is only the first part to get DM_VIDEO
> running properly on tbs2910 for u-boot-2020.10. With this, I get a valid
> video output signal, but no actual video console output, only a blank
> screen.
>
> After some debugging, no with access to a HDMI monitor, the problem
> seems to be:
> imx6q has two ipu units, so DM_VIDEO creates 2 video devices. For these
> two devices also memory for two framebuffers is reserved in
> video-uclass, starting from gd->video_top downwards. Then vidconsole
> correctly uses the first video device (ipu1), but apparently the
> framebuffer from ipu2 at gd->video_bottom. So I see the empty
> framebuffer from ipu1 while the console output goes to the framebuffer
> memory of ipu2.
Thanks for debugging and reporting!
> I guess there is the same problem on all imx6q devices with 2 ipu units,
> while on imx6s/6dl devices with a single ipu everything works fine.
> Disabling the second ipu in the tbs2910 devicetree also helps, but I
> think this is not a proper solution.
>
> What should be done about this? Only probing the first ipu/video device?
Since the second framebuffer is not in use currently, the probing for
second ipu device is not done.
> Assigning the framebuffer memory bottom-up? Using the assigned
> framebuffer memory of the active video device for console output (seems
> to be the correct solution, but maybe not so easy to implement)?
Yes, the later is the correct solution. I've sent a patch.
--
Anatolij
next prev parent reply other threads:[~2020-08-03 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 19:14 [BUG] DM_VIDEO broken on imx6q Soeren Moch
2020-08-03 13:54 ` Anatolij Gustschin [this message]
2020-08-03 15:13 ` Soeren Moch
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=20200803155424.78c67ad0@crub \
--to=agust@denx.de \
--cc=u-boot@lists.denx.de \
/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.