linux-kernel - Re: [PATCH v2 04/12] drm/sun4i: engine: Add a custom crtc atomic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGb2v66xxOL3XO8uFr2zVv4f6kzZHwWDDWJpYLz16Z0BxrSGwg@mail.gmail.com>
Date:   Tue, 19 Dec 2017 13:08:13 +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>, Chen-Yu Tsai <wens@...e.org>,
        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 04/12] drm/sun4i: engine: Add a custom crtc atomic_check

On Mon, Dec 18, 2017 at 10:57 PM, Maxime Ripard
<maxime.ripard@...e-electrons.com> wrote:
> We have some restrictions on what the planes and CRTC can provide that are
> tied to only one generation of display engines.
>
> For example, on the first generation, we can only have one YUV plane or one
> plane that uses the frontend output.
>
> Let's allow our engines to provide an atomic_check callback to validate the
> current configuration.
>
> 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>