From: "Ryan Walklin" <ryan@testtoast.com>
To: "Jernej Skrabec" <jernej.skrabec@gmail.com>,
"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>,
"Samuel Holland" <samuel@sholland.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>
Cc: "Andre Przywara" <andre.przywara@arm.com>,
"Chris Morgan" <macroalpha82@gmail.com>,
"Hironori KIKUCHI" <kikuchan98@gmail.com>,
"Philippe Simons" <simons.philippe@gmail.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v7 00/27] drm: sun4i: add Display Engine 3.3 (DE33) support
Date: Sun, 23 Feb 2025 12:26:17 +1300 [thread overview]
Message-ID: <44980f16-4b9c-4e49-92fa-af8b2677ca31@app.fastmail.com> (raw)
In-Reply-To: <7770397.EvYhyI6sBW@jernej-laptop>
On Sat, 22 Feb 2025, at 10:28 PM, Jernej Škrabec wrote:
> Sorry, completely forgot. YUV420 HDMI code relies on my previous work,
> with which
> Maxime wasn't happy with:
>
> https://lore.kernel.org/linux-sunxi/20230924192604.3262187-1-jernej.skrabec@gmail.com/
>
> So unless switching HDMI to bridge ops is implemented, which also
> brings format,
> YUV formatter and some other patches just add unused code, which isn't
> ideal,
> especially if we decide to rework driver before that code can be put in
> acceptable
> state for all involved.
>
> From quick look, patches 5-13, 26 should be dropped for now. Not sure about 1-4.
>
> I'm fine with AFBC support going in, it's just one patch.
Makes sense, ok I will prepare a pure DE33 patch with AFBC and RGB support, removing the YUV code. I think the CSC changes (1-4) are good to stay as it is a change that makes sense regardless and makes the YUV work a bit easier.
Thanks for the other clarifications and vendor code links, will do a bit of reading.
Regards,
Ryan
next prev parent reply other threads:[~2025-02-22 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 18:31 [PATCH v7 00/27] drm: sun4i: add Display Engine 3.3 (DE33) support Ryan Walklin
2025-02-16 18:32 ` [PATCH v7 01/27] drm: sun4i: de2/de3: Change CSC argument Ryan Walklin
2025-02-21 18:57 ` [PATCH v7 00/27] drm: sun4i: add Display Engine 3.3 (DE33) support Jernej Škrabec
2025-02-22 2:48 ` Ryan Walklin
2025-02-22 9:28 ` Jernej Škrabec
2025-02-22 23:26 ` Ryan Walklin [this message]
2025-02-23 15:53 ` Jernej Škrabec
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=44980f16-4b9c-4e49-92fa-af8b2677ca31@app.fastmail.com \
--to=ryan@testtoast.com \
--cc=airlied@gmail.com \
--cc=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=kikuchan98@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=macroalpha82@gmail.com \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=sboyd@kernel.org \
--cc=simons.philippe@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.