From: Anatolij Gustschin <agust@denx.de>
To: Tim Harvey <tharvey@gateworks.com>
Cc: u-boot <u-boot@lists.denx.de>, Fabio Estevam <festevam@gmail.com>,
Stefano Babic <sbabic@denx.de>
Subject: Re: imx6 DM_VIDEObroken
Date: Tue, 28 Sep 2021 14:55:19 +0200 [thread overview]
Message-ID: <20210928145519.649314fd@crub> (raw)
In-Reply-To: <CAJ+vNU0iGSN+gEycP8tH0kmq9L+Jos8Y+81MLtHwWRM-+ZcUNg@mail.gmail.com>
Hey Tim,
On Mon, 27 Sep 2021 17:25:58 -0700
Tim Harvey tharvey@gateworks.com wrote:
> Anatolij,
>
> Since commit d37618d18d49 ("imx: convert gwventana board to DM_VIDEO")
> video support for IMX6 based Ventana boards has been broken.
Back then I've tested similar DM_VIDEO conversion changes on i.mx6q
nitrogen6q board and on i.mx6d/i.mx6s wandboards, it was okay if
the board configuration uses the video console output during the
boot sequence (i.e. configured to show splash screen or to output
strings on vidconsole).
> I find that while the bind function for fsl_imx6q_ipu is called the
> probe never is (ipuv3_video_probe). Do you know why this is?
Is video console output used during the boot? If not, then it
might be the reason. With DM, the devices are probed when a subsystem
actually tries to use them. You can try to trigger probing via
switching to the video console output, i.e.:
=> setenv stdout vidconsole
>
> I see that with commit 57f065fee2a4 ("video: ipuv3: add DM_VIDEO
> support") you mention that DTS files must include
> 'u-boot,dm-pre-reloc' for soc/ipu nodes to enable driver binding to
> ipu device but I haven't been able to get that to make a difference
> nor have I found a board that does this. You did add those props to
> imx6qdl.dtsi at one point but they are no longer there.
Does your board dts include imx6qdl-u-boot.dtsi ?
The u-boot,dm-pre-reloc properties were moved to this U-Boot specific
dtsi in 7932b1c9fdb73393aa110249c89bd426533c0649
(imx: imx6qdl: dtsi: move U-Boot specific change to u-boot.dtsi)
> There must have been several other IMX6 boards with video support that
> were affected by this so perhaps I'm missing something simple.
I did not test it recently, it looks I'll have to do it before the
new release.
--
Anatolij
next prev parent reply other threads:[~2021-09-28 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 0:25 imx6 DM_VIDEObroken Tim Harvey
2021-09-28 12:55 ` Anatolij Gustschin [this message]
2021-09-28 17:00 ` Tim Harvey
2021-09-29 1:51 ` Fabio Estevam
2021-09-29 15:55 ` Tim Harvey
2021-09-29 16:33 ` Tim Harvey
2021-10-04 13:48 ` Anatolij Gustschin
2021-10-07 19:50 ` Tim Harvey
2021-10-07 21:55 ` Anatolij Gustschin
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=20210928145519.649314fd@crub \
--to=agust@denx.de \
--cc=festevam@gmail.com \
--cc=sbabic@denx.de \
--cc=tharvey@gateworks.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox