From: Maxime Jourdan <mjourdan@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org,
dri-devel@lists.freedesktop.org
Subject: [PATCH 0/2] drm/meson: Allow using optional canvas provider
Date: Mon, 5 Nov 2018 11:45:06 +0100 [thread overview]
Message-ID: <20181105104508.23090-1-mjourdan@baylibre.com> (raw)
The meson DRM driver currently uses constant, static canvas indexes.
This is not optimal and could conflict with other drivers also using
canvases.
This patch series allows the driver to optionnally use a canvas provider
module that is able to dispatch canvases, on demand and free of conflict.
In the future, the current way of doing things will be deprecated.
Maxime Jourdan (2):
dt-bindings: display: amlogic, meson-vpu: Add optional canvas provider
node
drm/meson: Use optional canvas provider
.../bindings/display/amlogic,meson-vpu.txt | 2 +
drivers/gpu/drm/meson/Kconfig | 1 +
drivers/gpu/drm/meson/meson_crtc.c | 14 ++++--
drivers/gpu/drm/meson/meson_drv.c | 46 ++++++++++++-------
drivers/gpu/drm/meson/meson_drv.h | 4 ++
drivers/gpu/drm/meson/meson_plane.c | 8 +++-
6 files changed, 53 insertions(+), 22 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-05 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 10:45 Maxime Jourdan [this message]
2018-11-05 10:45 ` [PATCH 1/2] dt-bindings: display: amlogic, meson-vpu: Add optional canvas provider node Maxime Jourdan
2018-11-05 10:45 ` [PATCH 2/2] drm/meson: Use optional canvas provider Maxime Jourdan
2018-11-05 12:53 ` Neil Armstrong
2018-11-05 12:51 ` [PATCH 0/2] drm/meson: Allow using " Neil Armstrong
2018-11-05 14:02 ` Maxime Jourdan
2018-11-13 13:32 ` Neil Armstrong
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=20181105104508.23090-1-mjourdan@baylibre.com \
--to=mjourdan@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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;
as well as URLs for NNTP newsgroup(s).