From: Neil Armstrong <narmstrong@baylibre.com>
To: Maxime Jourdan <mjourdan@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: Re: [PATCH 0/2] drm/meson: Allow using optional canvas provider
Date: Tue, 13 Nov 2018 14:32:36 +0100 [thread overview]
Message-ID: <ec49e7c1-8ca6-b442-10dc-1f15a15917bc@baylibre.com> (raw)
In-Reply-To: <CAMO6nax_Q4kbDkeBmYQezo9dpMztD4DMFh+1dewax4p6d_S7mw@mail.gmail.com>
On 05/11/2018 15:02, Maxime Jourdan wrote:
> Hi Neil,
>
> On Mon, Nov 5, 2018 at 1:51 PM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>
>> Hi Maxime,
>>
>> On 05/11/2018 11:45, Maxime Jourdan wrote:
>>> The meson DRM driver currently uses constant, static canvas indexes.
>>>
>>> This is not optimal and could conflict with other drivers also using
>>> canvases.
>>
>> Indeed, it's now time to use the canvas provider merged in 4.20-rc1 !
>>
>>>
>>> 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.
>>
>> Do you confirm you will send a patch to remove the legacy canvas code when
>> everything is merged (including DT changes) ?
>>
>> I'll wait until the bindings are reviewed, then I'll push the serie to drm-misc-next.
>>
>
> Yes, ultimately it will be removed.
>
> The plan is:
>
> 4.21: allow using both modes, add the "amlogic,canvas" property to the dts files
> 4.22: remove the old way and change the amlogic,canvas property to mandatory
>
> This should allow for a nice transition.
>
> Maxime
>
>> Thanks,
>> Neil
>>
>>>
>>> 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(-)
>>>
Applied
prev parent reply other threads:[~2018-11-13 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 10:45 [PATCH 0/2] drm/meson: Allow using optional canvas provider Maxime Jourdan
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 [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=ec49e7c1-8ca6-b442-10dc-1f15a15917bc@baylibre.com \
--to=narmstrong@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=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).