[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3382705.44csPzL39Z@jernej-laptop>
Date: Mon, 27 Oct 2025 19:11:52 +0100
From: Jernej Škrabec <jernej.skrabec@...il.com>
To: wens@...e.org
Cc: mripard@...nel.org, maarten.lankhorst@...ux.intel.com,
tzimmermann@...e.de, airlied@...il.com, simona@...ll.ch, samuel@...lland.org,
dri-devel@...ts.freedesktop.org, linux-arm-kernel@...ts.infradead.org,
linux-sunxi@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 07/30] drm/sun4i: Move blender config from layers to mixer
Dne ponedeljek, 27. oktober 2025 ob 17:00:05 Srednjeevropski standardni čas je Chen-Yu Tsai napisal(a):
> On Mon, Oct 13, 2025 at 3:23 AM Jernej Skrabec <jernej.skrabec@...il.com> wrote:
> >
> > With upcoming DE33 support, layer management must be decoupled from
> > other operations like blender configuration. There are two reasons:
> > - DE33 will have separate driver for planes and thus it will be harder
> > to manage different register spaces
>
> So if I understand correctly:
>
> - the "layer" is from DMA up to CSC, which is the last stage before routing
> - in DE30 and before, routing was limited to within one mixer
> - in DE33 and onward, routing is global
If you mean routing layers, then yes.
For example, you have pool of 4 UI planes and 3 VI planes. You can assign them
in any combination to both mixers. Later you have additional Z-pos routing too
within mixer.
>
> > - Architecturaly it's better to split access by modules. Blender is now
> > exclusively managed by mixer.
> >
> > Signed-off-by: Jernej Skrabec <jernej.skrabec@...il.com>
>
> Reviewed-by: Chen-Yu Tsai <wens@...nel.org>
>
Thanks.
Best regards,
Jernej
Powered by blists - more mailing lists