From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
"open list:BAREBOX" <barebox@lists.infradead.org>
Subject: Re: [PATCH 11/13] fb: print more information on devinfo
Date: Fri, 27 Sep 2024 08:16:17 +0200 [thread overview]
Message-ID: <ac303060-40ed-431b-a4d8-084c2bb3632c@pengutronix.de> (raw)
In-Reply-To: <20240926-vop2-v1-11-fe0581f2020b@pengutronix.de>
On 26.09.24 15:15, Sascha Hauer wrote:
> Print some more information about the framebuffer in the devinfo output:
> - x/y resolution
> - line_length
> - type of framebuffer (overlay, base plane)
> - if it's an overlay, print the base plane
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> drivers/video/fb.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/video/fb.c b/drivers/video/fb.c
> index 3677c63e07..f6310498c8 100644
> --- a/drivers/video/fb.c
> +++ b/drivers/video/fb.c
> @@ -264,6 +264,15 @@ static void fb_info(struct device *dev)
> printf("Available modes:\n");
> fb_print_modes(&info->modes);
> fb_print_modes(&info->edid_modes);
> + if (info->base) {
Having both screen_base and unadorned base in the same struct is confusing.
How about renaming this to base_plane?
Also, to make this a bit more convenient to use, should we make overlays
a "partition" of the original fb device? /dev/fb0 (base), /dev/fb0.\d (overlays).
> + printf("Type: overlay\n");
> + printf("base plane: %s\n", dev_name(&info->base->dev));
> + } else {
> + printf("Type: primary\n");
> + }
> + printf("xres: %u\n", info->xres);
> + printf("yres: %u\n", info->yres);
> + printf("line_length: %u\n", info->line_length);
> }
>
> void *fb_get_screen_base(struct fb_info *info)
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-09-27 6:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 13:14 [PATCH 00/13] video: Add Rockchip VOP2 support Sascha Hauer
2024-09-26 13:14 ` [PATCH 01/13] clk: rockchip: rk3568: Fix HDMI clocks Sascha Hauer
2024-09-26 14:19 ` Ahmad Fatoum
2024-09-26 13:15 ` [PATCH 02/13] video: add videomode helpers Sascha Hauer
2024-09-26 13:15 ` [PATCH 03/13] media-bus-format: update from kernel Sascha Hauer
2024-09-26 14:20 ` Ahmad Fatoum
2024-09-26 13:15 ` [PATCH 04/13] regmap: add regfield support Sascha Hauer
2024-09-26 13:15 ` [PATCH 05/13] video: add include/video/drm/drm_connector.h Sascha Hauer
2024-09-26 13:15 ` [PATCH 06/13] fb: add fb_rect functions Sascha Hauer
2024-09-26 13:15 ` [PATCH 07/13] video: Add Sitronix st7789v panel driver Sascha Hauer
2024-09-26 14:16 ` Ahmad Fatoum
2024-09-27 10:15 ` Sascha Hauer
2024-09-26 13:15 ` [PATCH 08/13] video: add dw-hdmi driver Sascha Hauer
2024-09-26 13:15 ` [PATCH 09/13] video: i.MX ipuv3: switch to upstream hdmi driver Sascha Hauer
2024-09-27 6:18 ` Ahmad Fatoum
2024-09-26 13:15 ` [PATCH 10/13] fb: Accept overlay framebuffers without modes Sascha Hauer
2024-09-26 13:15 ` [PATCH 11/13] fb: print more information on devinfo Sascha Hauer
2024-09-27 6:16 ` Ahmad Fatoum [this message]
2024-09-26 13:15 ` [PATCH 12/13] ARM: ARM64: implement dma_alloc_writecombine() Sascha Hauer
2024-09-26 14:24 ` Ahmad Fatoum
2024-09-26 13:15 ` [PATCH 13/13] video: Rockchip: Add VOP2 driver Sascha Hauer
2024-09-27 6:13 ` Ahmad Fatoum
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=ac303060-40ed-431b-a4d8-084c2bb3632c@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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