Thomas Zimmermann <tzimmerm...@suse.de> writes:
> Set fbdev default flags FBNFO_DEFAULT and mark the framebuffer with
> FBINFO_VIRTFB. The framebuffer range is in DMA-able memory and should
> be accessed with the CPU's regular memory ops.
>
> Signed-off-by: Thomas Zimmermann <tzimmerm...@suse.de>
> Cc: Thierry Reding <thierry.red...@gmail.com>
> Cc: Mikko Perttunen <mperttu...@nvidia.com>
> ---
> drivers/gpu/drm/tegra/fbdev.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/tegra/fbdev.c b/drivers/gpu/drm/tegra/fbdev.c
> index 82577b7c88da..8074430c52f1 100644
> --- a/drivers/gpu/drm/tegra/fbdev.c
> +++ b/drivers/gpu/drm/tegra/fbdev.c
> @@ -103,6 +103,8 @@ static int tegra_fbdev_probe(struct drm_fb_helper *helper,
> return PTR_ERR(info);
> }
>
> + info->flags = FBINFO_DEFAULT;
> +
> fb = tegra_fb_alloc(drm, &cmd, &bo, 1);
> if (IS_ERR(fb)) {
> err = PTR_ERR(fb);
> @@ -132,6 +134,7 @@ static int tegra_fbdev_probe(struct drm_fb_helper *helper,
> }
> }
>
> + info->flags |= FBINFO_VIRTFB;
I see that all fbdev drivers just do: info->flags = FBINFO_FLAG_DEFAULT |
FBINFO_VIRTFB
Guess you are doing in two assignments to be consistent with drm_fbdev_dma.c ?
I was just curious about the rationale for setting the flags in two steps.
Reviewed-by: Javier Martinez Canillas <javi...@redhat.com>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
