[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGb2v66j9hhFue1x1HO_a3RULUP_qWL7ivZLGeYQRwdph2Md+A@mail.gmail.com>
Date: Thu, 4 Jan 2018 23:49:04 +0800
From: Chen-Yu Tsai <wens@...e.org>
To: Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc: Daniel Vetter <daniel.vetter@...el.com>,
David Airlie <airlied@...ux.ie>,
dri-devel <dri-devel@...ts.freedesktop.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Neil Armstrong <narmstrong@...libre.com>, thomas@...sch.nl
Subject: Re: [PATCH v2 09/12] drm/sun4i: backend: Add a custom atomic_check
for the frontend
On Mon, Dec 18, 2017 at 10:57 PM, Maxime Ripard
<maxime.ripard@...e-electrons.com> wrote:
> Now that we have everything in place, we can start enabling the frontend.
> This is more difficult than one would assume since there can only be one
> plane using the frontend per-backend.
>
> We therefore need to make sure that the userspace will not try to setup
> multiple planes using it, since that would be impossible. In order to
> prevent that, we can create an atomic_check callback that will check that
> only one plane will effectively make use of the frontend in a given
> configuration, and will toggle the switch in that plane state so that the
> proper setup function can do their role.
>
> Reviewed-by: Neil Armstrong <narmstrong@...libre.com>
> Signed-off-by: Maxime Ripard <maxime.ripard@...e-electrons.com>
Reviewed-by: Chen-Yu Tsai <wens@...e.org>
Powered by blists - more mailing lists