From: Stefan Lengfeld <contact@stefanchrist.eu>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
David Airlie <airlied@linux.ie>,
Sean Paul <seanpaul@chromium.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4 1/1] drm/fb-helper: implement ioctl FBIO_WAITFORVSYNC
Date: Sun, 5 Mar 2017 23:23:28 +0100 [thread overview]
Message-ID: <20170305222328.GA25089@sill.h.stcim.de> (raw)
In-Reply-To: <9f67ae4055ab0bc093d7d94e503a0d6d1909d856.1488296169.git-series.maxime.ripard@free-electrons.com>
Hi Maxime,
On Tue, Feb 28, 2017 at 04:36:51PM +0100, Maxime Ripard wrote:
> Implement legacy framebuffer ioctl FBIO_WAITFORVSYNC in the generic
> framebuffer emulation driver. Legacy framebuffer users like non kms/drm
> based OpenGL(ES)/EGL implementations may require the ioctl to
> synchronize drawing or buffer flip for double buffering. It is tested on
> the i.MX6.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> Tested-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
> drivers/gpu/drm/drm_fb_helper.c | 68 ++++++++++++++++++++++++++++++++++-
> include/drm/drm_fb_helper.h | 12 +++++-
> 2 files changed, 79 insertions(+), 1 deletion(-)
I have tested the current HEAD of drm-misc-next. It includes this patch
and the patch ("drm/fb-helper: Add multi buffer support for cma fbdev").
On my i.MX6 board with HDMI output both patches work as advertised.
Multi-buffering with ioctls FBIO_WAITFORVSYNC and FBIOPAN_DISPLAY is
possible.
Kind Regards
Stefan Lengfeld
prev parent reply other threads:[~2017-03-05 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 15:36 [PATCH v4 0/1] drm: Support framebuffer panning Maxime Ripard
2017-02-28 15:36 ` [PATCH v4 1/1] drm/fb-helper: implement ioctl FBIO_WAITFORVSYNC Maxime Ripard
2017-03-01 21:31 ` Stefan Lengfeld
2017-03-02 7:12 ` Daniel Vetter
2017-03-02 10:09 ` Daniel Vetter
2017-03-05 22:23 ` Stefan Lengfeld [this message]
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=20170305222328.GA25089@sill.h.stcim.de \
--to=contact@stefanchrist.eu \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=seanpaul@chromium.org \
/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
all inboxes | Powered by JetHome®