U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Anatolij Gustschin <agust@denx.de>
Cc: Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH] WIP: Nokia RX-51: Convert to CONFIG_DM_VIDEO
Date: Sun, 6 Mar 2022 12:51:41 +0100	[thread overview]
Message-ID: <20220306115141.gb4y6fsgqmrtg4ce@pali> (raw)
In-Reply-To: <20220217122043.nhjd7o467pkcrnas@pali>

PING?

On Thursday 17 February 2022 13:20:43 Pali Rohár wrote:
> On Thursday 17 February 2022 09:53:39 Anatolij Gustschin wrote:
> > Hi Pali,
> > 
> > On Wed, 16 Feb 2022 21:42:19 +0100
> > Pali Rohár pali@kernel.org wrote:
> > 
> > > ---
> > > I had to comment "return -ENOSPC;" in video-uclass.c because without it
> > > DM_VIDEO does not work and I do not know why. This looks like either
> > > false-positive test or a bug in DM_VIDEO code. I have already set
> > > PRE_RELOC flag but it has no effect on that code.
> > 
> > Probably the frame buffer memory allocation did not work. 
> > Could you please try with a bind callback, i.e.:
> > 
> > static int rx51_video_bind(struct udevice *dev)
> > {
> > 	struct video_uc_plat *plat = dev_get_uclass_plat(dev);
> > 
> > 	plat->size = 800 * 480 * 2;
> > 	return 0;
> > }
> > ...
> > U_BOOT_DRIVER(rx51_video) = {
> > 	.name = "rx51_video",
> > 	.id = UCLASS_VIDEO,
> > 	.bind = rx51_video_bind,
> > 	.probe = rx51_video_probe,
> > 	.flags = DM_FLAG_PRE_RELOC,
> > };
> 
> Hello! It does not work too. Here is the output:
> 
> U-Boot 2022.04-rc2-00002-ga2c1a9878375-dirty (Jan 01 1970 - 00:00:00 +0000)
> 
> OMAP35XX-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 MHz
> DRAM:  Video frame buffers from 8fe30000 to 8fe30000
> 256 MiB
> Video device 'rx51_video' cannot allocate frame buffer memory -ensure the device is set up before relocation
> 
> If "return -ENOSPC;" is not commented then this is the last printed
> line. If it is commented then output continues with:
> 
> video_post_bind: Claiming 130000 bytes at 8fd00000 for video device 'rx51_video'
> 
> And framebuffer is working fine like without above rx51_video_bind()
> change.
> 
> > > 
> > > Second thing is that CONFIG_VIDEO_LOGO is broken and does not work even it
> > > is enabled in config file. I do not know why too.
> > > 
> > > Any idea?
> > 
> > Not yet. There were some logo related changes recently, but if I
> > remember correctly, I tested them on wandboard and nitrogen6q
> > targets and with sandbox, and logo drawing worked there.
> > 
> > --
> > Anatolij

  reply	other threads:[~2022-03-06 11:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 20:42 [PATCH] WIP: Nokia RX-51: Convert to CONFIG_DM_VIDEO Pali Rohár
2022-02-17  8:53 ` Anatolij Gustschin
2022-02-17 12:20   ` Pali Rohár
2022-03-06 11:51     ` Pali Rohár [this message]
2022-03-06 12:51       ` Simon Glass
2022-03-06 14:17         ` Pali Rohár
2022-03-06 14:42           ` Simon Glass
2022-03-06 15:25             ` Pali Rohár
2022-03-06 18:44               ` Simon Glass
2022-03-09 19:44                 ` Pali Rohár
2022-03-09 22:20                   ` Anatolij Gustschin
2022-03-11 18:58                     ` Pali Rohár
2022-03-12  5:02                       ` Simon Glass
2022-03-13 11:06                         ` Pali Rohár
2022-03-06 15:08 ` [PATCH] " Pali Rohár
2022-03-06 18:43   ` Simon Glass
2022-03-09 19:37     ` Pali Rohár
2022-03-09 19:46 ` [PATCH v2 1/2] video: Allow drivers to allocate the frame buffer themselves Pali Rohár
2022-03-09 19:46   ` [PATCH v2 2/2] Nokia RX-51: Convert to CONFIG_DM_VIDEO Pali Rohár
2022-03-14 22:42     ` Anatolij Gustschin
2022-03-12  2:43   ` [PATCH v2 1/2] video: Allow drivers to allocate the frame buffer themselves Simon Glass
2022-03-14 22:41   ` 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=20220306115141.gb4y6fsgqmrtg4ce@pali \
    --to=pali@kernel.org \
    --cc=agust@denx.de \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.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