From: Marek Vasut <marex@denx.de>
To: Philipp Zabel <p.zabel@pengutronix.de>, linux-media@vger.kernel.org
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Helge Deller <deller@gmx.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Steve Longerbeam <slongerbeam@gmail.com>,
dri-devel@lists.freedesktop.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v2 1/2] gpu: ipu-v3: vdic: Simplify ipu_vdi_setup()
Date: Wed, 25 Sep 2024 21:47:51 +0200 [thread overview]
Message-ID: <a8fb73cd-afc1-4bf9-8a3d-e0815530d680@denx.de> (raw)
In-Reply-To: <75edf945c98a68bf85b13efd1c13549288f56488.camel@pengutronix.de>
On 9/25/24 6:43 PM, Philipp Zabel wrote:
> On Di, 2024-09-24 at 12:47 +0200, Marek Vasut wrote:
>> On 9/4/24 11:05 AM, Philipp Zabel wrote:
>>> On Mi, 2024-07-24 at 02:19 +0200, Marek Vasut wrote:
>>>> The 'code' parameter only ever selects between YUV 4:2:0 and 4:2:2
>>>> subsampling, turn it into boolean to select exactly that and update
>>>> related code accordingly.
>>>>
>>>> Signed-off-by: Marek Vasut <marex@denx.de>
>>>
>>> I'd prefer this to be an enum ipu_chroma_subsampling or similar,
>>> instead of a boolean. Otherwise,
>>
>> I'm afraid this introduces unnecessary back and forth conversions
>> between the boolean and either of the two enum ipu_chroma_subsampling
>> values in the code.
>
> Fair enough. I dislike the opaque usage in vdic_start() a bit, but with
> the in422 variable in ipu_mem2mem_vdic_setup_hardware() it is clear
> enough.
I'll keep the rework for V3 and then we can decide whether or not to
undo it.
prev parent reply other threads:[~2024-09-25 20:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 0:19 [PATCH v2 1/2] gpu: ipu-v3: vdic: Simplify ipu_vdi_setup() Marek Vasut
2024-07-24 0:19 ` [PATCH v2 2/2] media: imx: vdic: Introduce mem2mem VDI deinterlacer driver Marek Vasut
2024-07-24 16:08 ` Nicolas Dufresne
2024-07-29 2:16 ` Marek Vasut
2024-07-30 16:05 ` Nicolas Dufresne
2024-09-24 15:42 ` Marek Vasut
2024-10-15 17:31 ` Nicolas Dufresne
2024-07-24 16:16 ` Dan Carpenter
2024-07-29 2:19 ` Marek Vasut
2024-09-06 9:01 ` Philipp Zabel
2024-09-24 15:28 ` Marek Vasut
2024-09-25 15:07 ` Philipp Zabel
2024-09-25 20:14 ` Marek Vasut
2024-09-26 11:14 ` Philipp Zabel
2024-10-03 15:11 ` Marek Vasut
2024-10-15 17:46 ` Nicolas Dufresne
2024-09-25 17:58 ` Nicolas Dufresne
2024-09-25 20:45 ` Marek Vasut
2024-09-26 11:16 ` Philipp Zabel
2024-10-03 14:57 ` Marek Vasut
2024-10-08 14:23 ` Philipp Zabel
2024-10-15 18:13 ` Nicolas Dufresne
2024-09-27 19:33 ` Nicolas Dufresne
2024-10-03 17:13 ` Marek Vasut
2024-09-04 9:05 ` [PATCH v2 1/2] gpu: ipu-v3: vdic: Simplify ipu_vdi_setup() Philipp Zabel
2024-09-24 10:47 ` Marek Vasut
2024-09-25 16:43 ` Philipp Zabel
2024-09-25 19:47 ` Marek Vasut [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=a8fb73cd-afc1-4bf9-8a3d-e0815530d680@denx.de \
--to=marex@denx.de \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=slongerbeam@gmail.com \
/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 NNTP newsgroup(s).