dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: stefan@agner.ch
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/tegra: fb: Implement ->fb_mmap() callback
Date: Wed, 07 Feb 2018 20:24:37 +0100	[thread overview]
Message-ID: <38cadc9d2e10559c3a8d3eab479ec6cb@agner.ch> (raw)
In-Reply-To: <20180207174556.25401-3-thierry.reding@gmail.com>

On 07.02.2018 18:45, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> This fixes hangs with legacy applications that use the mmap() syscall on
> the fbdev device to map framebuffer memory. The fbdev implementation for
> mmap() creates a mapping that conflicts with DRM usage and causes a hang
> when the memory is accessed through the mapping.

That helps using applications making use of mmap & fbdev on an Apalis
TK1!

Tested-by: Stefan Agner <stefan@agner.ch>

--
Stefan

> 
> Reported-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
>  drivers/gpu/drm/tegra/fb.c | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/drivers/gpu/drm/tegra/fb.c b/drivers/gpu/drm/tegra/fb.c
> index 001cb77e2f59..0786159edef3 100644
> --- a/drivers/gpu/drm/tegra/fb.c
> +++ b/drivers/gpu/drm/tegra/fb.c
> @@ -224,12 +224,28 @@ struct drm_framebuffer *tegra_fb_create(struct
> drm_device *drm,
>  }
>  
>  #ifdef CONFIG_DRM_FBDEV_EMULATION
> +static int tegra_fb_mmap(struct fb_info *info, struct vm_area_struct *vma)
> +{
> +	struct drm_fb_helper *helper = info->par;
> +	struct tegra_bo *bo;
> +	int err;
> +
> +	bo = tegra_fb_get_plane(helper->fb, 0);
> +
> +	err = drm_gem_mmap_obj(&bo->gem, bo->gem.size, vma);
> +	if (err < 0)
> +		return err;
> +
> +	return __tegra_gem_mmap(&bo->gem, vma);
> +}
> +
>  static struct fb_ops tegra_fb_ops = {
>  	.owner = THIS_MODULE,
>  	DRM_FB_HELPER_DEFAULT_OPS,
>  	.fb_fillrect = drm_fb_helper_sys_fillrect,
>  	.fb_copyarea = drm_fb_helper_sys_copyarea,
>  	.fb_imageblit = drm_fb_helper_sys_imageblit,
> +	.fb_mmap = tegra_fb_mmap,
>  };
>  
>  static int tegra_fbdev_probe(struct drm_fb_helper *helper,
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-02-07 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 17:45 [PATCH 1/3] drm/tegra: gem: Reshuffle declarations Thierry Reding
     [not found] ` <20180207174556.25401-1-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-07 17:45   ` [PATCH 2/3] drm/tegra: gem: Make __tegra_gem_mmap() available more widely Thierry Reding
2018-02-07 17:45   ` [PATCH 3/3] drm/tegra: fb: Implement ->fb_mmap() callback Thierry Reding
2018-02-07 19:24     ` stefan [this message]
     [not found]     ` <20180207174556.25401-3-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-08  0:52       ` Marcel Ziswiler

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=38cadc9d2e10559c3a8d3eab479ec6cb@agner.ch \
    --to=stefan@agner.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=marcel.ziswiler@toradex.com \
    --cc=thierry.reding@gmail.com \
    /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