From: Neil Armstrong <narmstrong@baylibre.com>
To: Maxime Jourdan <mjourdan@baylibre.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] drm/meson: only allow using meson-canvas
Date: Wed, 20 Mar 2019 09:42:25 +0100 [thread overview]
Message-ID: <7c9b4a05-bfc6-39d9-f8cf-6698a7b2e3e7@baylibre.com> (raw)
In-Reply-To: <375bb9db-50bb-000a-077b-6f090ae73039@baylibre.com>
On 13/03/2019 13:50, Neil Armstrong wrote:
> On 11/03/2019 11:51, Maxime Jourdan wrote:
>> This patch series aims at removing access to the DMC register range from
>> the meson DRM driver, and is the final step at fully migrating it to using
>> the meson canvas provider module.
>>
>> Please see the commit notes of patch 1/2
>> "dt-bindings: display: amlogic, meson-vpu: exclusively use amlogic,canvas"
>> for more information.
>>
>> This series also incorporates a probing fix proposed by Neil Armstrong [1]
>> although rewritten because of heavy code changes in the corresponding
>> location.
>>
>> [1] https://lkml.org/lkml/2019/2/4/152
>>
>> Maxime Jourdan (2):
>> dt-bindings: display: amlogic, meson-vpu: exclusively use
>> amlogic,canvas
>> drm/meson: exclusively use the canvas provider module
>>
>> .../bindings/display/amlogic,meson-vpu.txt | 5 +-
>> drivers/gpu/drm/meson/Makefile | 2 +-
>> drivers/gpu/drm/meson/meson_canvas.c | 73 ----------------
>> drivers/gpu/drm/meson/meson_canvas.h | 51 -----------
>> drivers/gpu/drm/meson/meson_crtc.c | 84 ++++++-------------
>> drivers/gpu/drm/meson/meson_drv.c | 68 ++++++---------
>> drivers/gpu/drm/meson/meson_drv.h | 1 -
>> drivers/gpu/drm/meson/meson_overlay.c | 8 --
>> drivers/gpu/drm/meson/meson_plane.c | 6 +-
>> drivers/gpu/drm/meson/meson_viu.c | 1 -
>> 10 files changed, 53 insertions(+), 246 deletions(-)
>> delete mode 100644 drivers/gpu/drm/meson/meson_canvas.c
>> delete mode 100644 drivers/gpu/drm/meson/meson_canvas.h
>>
>
> Will apply on drm-misc-next for 5.2 when ready !
>
> Neil
>
Applied.
prev parent reply other threads:[~2019-03-20 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 10:51 [PATCH 0/2] drm/meson: only allow using meson-canvas Maxime Jourdan
2019-03-11 10:51 ` [PATCH 1/2] dt-bindings: display: amlogic, meson-vpu: exclusively use amlogic,canvas Maxime Jourdan
2019-03-13 12:49 ` Neil Armstrong
2019-03-11 10:51 ` [PATCH 2/2] drm/meson: exclusively use the canvas provider module Maxime Jourdan
2019-03-13 12:49 ` Neil Armstrong
2019-03-13 12:50 ` [PATCH 0/2] drm/meson: only allow using meson-canvas Neil Armstrong
2019-03-20 8:42 ` 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=7c9b4a05-bfc6-39d9-f8cf-6698a7b2e3e7@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjourdan@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).