From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: "Ondřej Jirman" <megi@xff.cz>,
linux-kernel@vger.kernel.org,
"Maxime Ripard" <mripard@kernel.org>,
"Chen-Yu Tsai" <wens@csie.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v2 0/3] Move blender setup from individual planes to crtc commit in sun4i-drm
Date: Sun, 21 Apr 2024 21:52:58 +0200 [thread overview]
Message-ID: <2725781.mvXUDI8C0e@jernej-laptop> (raw)
In-Reply-To: <wynuwtyn2skchb7gc5qixql2pxnb2nqvbmrda6s53u7nt5ki7n@hqb46kttkhee>
Dne petek, 19. april 2024 ob 15:36:17 GMT +2 je Ondřej Jirman napisal(a):
> Hi,
>
> On Sat, Feb 24, 2024 at 04:05:57PM GMT, megi xff wrote:
> > From: Ondrej Jirman <megi@xff.cz>
> >
> > This series refactors blender setup from individual planes to a common
> > place where it can be performed at once and is easier to reason about.
> >
> > In the process this fixes a few bugs that allowed blender pipes to be
> > disabled while corresponding DRM planes were requested to be enabled.
> >
> > Please take a look. :)
> >
> > v2:
> > - use regmap_write where possible
> > - add review tags
>
> It would be nice to have this applied.
Maxime,
do you mind applying?
Best regards,
Jernej
>
> Kind regards,
> o.
>
> > Thank you very much,
> > Ondřej Jirman
> >
> > Ondrej Jirman (3):
> > drm/sun4i: Unify sun8i_*_layer structs
> > drm/sun4i: Add more parameters to sunxi_engine commit callback
> > drm/sun4i: Fix layer zpos change/atomic modesetting
> >
> > drivers/gpu/drm/sun4i/sun4i_backend.c | 4 +-
> > drivers/gpu/drm/sun4i/sun4i_crtc.c | 2 +-
> > drivers/gpu/drm/sun4i/sun8i_mixer.c | 70 ++++++++++++++++++++-
> > drivers/gpu/drm/sun4i/sun8i_mixer.h | 20 ++++++
> > drivers/gpu/drm/sun4i/sun8i_ui_layer.c | 85 +++----------------------
> > drivers/gpu/drm/sun4i/sun8i_ui_layer.h | 20 ++----
> > drivers/gpu/drm/sun4i/sun8i_vi_layer.c | 86 +++-----------------------
> > drivers/gpu/drm/sun4i/sun8i_vi_layer.h | 20 ++----
> > drivers/gpu/drm/sun4i/sunxi_engine.h | 13 +++-
> > 9 files changed, 125 insertions(+), 195 deletions(-)
> >
>
prev parent reply other threads:[~2024-04-21 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 15:05 [PATCH v2 0/3] Move blender setup from individual planes to crtc commit in sun4i-drm Ondřej Jirman
2024-02-24 15:05 ` [PATCH v2 1/3] drm/sun4i: Unify sun8i_*_layer structs Ondřej Jirman
2024-02-24 15:05 ` [PATCH v2 2/3] drm/sun4i: Add more parameters to sunxi_engine commit callback Ondřej Jirman
2024-02-24 15:06 ` [PATCH v2 3/3] drm/sun4i: Fix layer zpos change/atomic modesetting Ondřej Jirman
2024-04-19 13:36 ` [PATCH v2 0/3] Move blender setup from individual planes to crtc commit in sun4i-drm Ondřej Jirman
2024-04-21 19:52 ` Jernej Škrabec [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=2725781.mvXUDI8C0e@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=megi@xff.cz \
--cc=mripard@kernel.org \
--cc=samuel@sholland.org \
--cc=tzimmermann@suse.de \
--cc=wens@csie.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).