From: Neil Armstrong <narmstrong@baylibre.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>,
Daniel Vetter <daniel.vetter@intel.com>,
David Airlie <airlied@linux.ie>,
Sean Paul <seanpaul@chromium.org>,
Jani Nikula <jani.nikula@linux.intel.com>
Cc: Stefan Christ <s.christ@phytec.de>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>
Subject: Re: [PATCH v3 0/2] drm: Support framebuffer panning
Date: Thu, 16 Feb 2017 17:40:08 +0100 [thread overview]
Message-ID: <6f108ce7-1e36-0177-2c23-c62fab6ebaad@baylibre.com> (raw)
In-Reply-To: <cover.9f4059bcaf1fdad78828633aa7815ba80384b24e.1487175046.git-series.maxime.ripard@free-electrons.com>
On 02/15/2017 05:19 PM, Maxime Ripard wrote:
> Hi,
>
> This is a respin of the previous serie called "Support fast framebuffer
> panning for i.MX6" made by Stefan 6 monthes ago. The imx6 bits have been
> removed, and the comments that were made at that time fixed (hopefully).
>
> Let me know what you think,
> Maxime
>
> Changes from v2:
> - Renamed the CONFIG_DRM_CMA_FBDEV_BUFFER_NUM to
> CONFIG_DRM_FBDEV_OVERALLOC, and changed it for a percentage
> - Moved the overallocation code into the core fbdev helpers to not rely
> on CMA anymore
> - Changed the locks taken by drm_fb_helper_ioctl to the mode_config mutex
> intead of calling drm_modeset_lock_all
> - Don't test against drm_crtc's enabled anymore, but rely on the error
> code of drm_crtc_vblank_get instead
> - Defined drm_fb_helper_ioctl when DRM_FBDEV_EMULATION is not set in
> order to fix a compilation error
> - Don't wait for all CRTC's vblank but only the one given in the ioctl
> argument
>
> Changes from v1:
> - Added drm_fb_helper_ioctl to DRM_FB_HELPER_DEFAULT_OPS
> - Expanded a bit the kerneldoc for drm_fb_helper_ioctl
> - Added some locking to drm_fb_helper_ioctl
> - Checked that the framebuffer is indeed attached before allowing ioctl
> - Added a module parameter to specify the number of framebuffers to
> allocate
>
> Initial cover letter: Support fast framebuffer panning for i.MX6
>
> im currently working on supporting double/tripple buffering for the
> framebuffer emulation on the i.MX6. While working on it I noticed that the
> mainline kernel does not support some features in the generic drm
> framebuffer emulation for framebuffer panning and vsync synchronisation.
> They are needed for simple framebuffer applications and some OpenGL
> libraries using double buffering with FBIOPUT_VSCREENINFO,
> FBIO_WAITFORVSYNC and FBIOPAN_DISPLAY.
>
> Stefan Christ (1):
> drm/fb-helper: implement ioctl FBIO_WAITFORVSYNC
>
> Xinliang Liu (1):
> drm/fb-helper: Add multi buffer support for cma fbdev
>
> drivers/gpu/drm/Kconfig | 9 ++++-
> drivers/gpu/drm/drm_fb_helper.c | 73 ++++++++++++++++++++++++++++++++++-
> include/drm/drm_fb_helper.h | 12 +++++-
> 3 files changed, 93 insertions(+), 1 deletion(-)
>
> base-commit: 0879b944c95d65f7523d178d3addaebe84e510ec
>
Hi Maxime,
Just tested these patches on Amlogic GXBB to provide 3D Mali acceleration on framebuffer.
Tested-by: Neil Armstrong <narmstrong@baylibre.com>
Thanks,
Neil
prev parent reply other threads:[~2017-02-16 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 16:19 Maxime Ripard
2017-02-15 16:19 ` [PATCH v3 1/2] drm/fb-helper: Add multi buffer support for cma fbdev Maxime Ripard
2017-02-20 17:07 ` Stefan Lengfeld
2017-02-23 0:49 ` Maxime Ripard
2017-02-26 21:06 ` Daniel Vetter
2017-02-15 16:19 ` [PATCH v3 2/2] drm/fb-helper: implement ioctl FBIO_WAITFORVSYNC Maxime Ripard
2017-02-21 10:00 ` Stefan Lengfeld
2017-02-21 10:55 ` Ville Syrjälä
2017-02-23 0:52 ` Maxime Ripard
2017-02-23 9:02 ` Stefan Lengfeld
2017-02-26 21:11 ` Daniel Vetter
2017-02-22 7:05 ` Michel Dänzer
2017-02-16 16:40 ` Neil Armstrong [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=6f108ce7-1e36-0177-2c23-c62fab6ebaad@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=s.christ@phytec.de \
--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®