From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Jacopo Mondi <jacopo.mondi+renesas@ideasonboard.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v9] media: vsp1: Add VSPX support
Date: Tue, 6 May 2025 19:37:33 +0200 [thread overview]
Message-ID: <20250506173733.GA539397@ragnatech.se> (raw)
In-Reply-To: <20250506-b4-vspx-v9-1-d7d50a01f7b6@ideasonboard.com>
Hi Jacopo,
Thanks for this new version!
I will give this a good testing as soon as I have finished some
refactoring of the user of this. I had a comment I wanted to send for
v8, but seems I never did. So for now I will just post this incase you
need to do a v10 before I had time.
On 2025-05-06 18:32:23 +0200, Jacopo Mondi wrote:
.. snip ..
> +struct vsp1_dl_list;
> +struct vsp1_isp_job_desc {
> + struct {
> + unsigned int pairs;
> + dma_addr_t mem;
> + } config;
> + struct {
> + struct v4l2_format fmt;
I'm very happy to see this is now the only location for the format, nice
work! I wonder if we shall take it one step further and just record the
fourcc, width, height and bytesperline here? Or at switch to a
v4l2_pix_format struct?
The user of this field do not really support multi plane formats, nor do
it validate fmt.type field.
I recently hit a snag in the ISP driver using this interface where I
*think* the solution is to only allow single plane buffers to be used as
input to the ISP (V4L2_CAP_VIDEO_OUTPUT_MPLANE vs
V4L2_CAP_VIDEO_OUTPUT). While fixing the plumbing for this I ran across
this, sorry for not noticing before.
> + dma_addr_t mem;
> + } img;
> + struct vsp1_dl_list *dl;
> +};
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2025-05-06 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 16:32 [PATCH v9] media: vsp1: Add VSPX support Jacopo Mondi
2025-05-06 17:37 ` Niklas Söderlund [this message]
2025-05-07 12:28 ` Jacopo Mondi
2025-05-07 14:09 ` Niklas Söderlund
2025-05-07 21:24 ` Jacopo Mondi
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=20250506173733.GA539397@ragnatech.se \
--to=niklas.soderlund@ragnatech.se \
--cc=jacopo.mondi+renesas@ideasonboard.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.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