From: "Du, Bin" <bin.du@amd.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: mchehab@kernel.org, hverkuil@xs4all.nl,
bryan.odonoghue@linaro.org, sakari.ailus@linux.intel.com,
prabhakar.mahadev-lad.rj@bp.renesas.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
sultan@kerneltoast.com, pratap.nirujogi@amd.com,
benjamin.chan@amd.com, king.li@amd.com,
gjorgji.rosikopulos@amd.com, Phil.Jawich@amd.com,
Dominic.Antony@amd.com, mario.limonciello@amd.com,
richard.gong@amd.com, anson.tsao@amd.com
Subject: Re: [PATCH v3 5/7] media: platform: amd: isp4 video node and buffers handling added
Date: Fri, 5 Sep 2025 15:05:29 +0800 [thread overview]
Message-ID: <da070ae7-6347-4ce5-a0c1-11d1b0e491bf@amd.com> (raw)
In-Reply-To: <20250903100841.GC13448@pendragon.ideasonboard.com>
Thanks Laurent Pinchart,
On 9/3/2025 6:08 PM, Laurent Pinchart wrote:
> Hi Bin,
>
> Thank you for the patch.
>
> On Thu, Aug 28, 2025 at 06:08:09PM +0800, Bin Du wrote:
>> Isp video implements v4l2 video interface and supports NV12 and YUYV. It
>> manages buffers, pipeline power and state. Cherry-picked Sultan's DMA
>> buffer realated fix from branch v6.16-drm-tip-isp4-for-amd on
>> https://github.com/kerneltoast/kernel_x86_laptop.git
>>
>> Co-developed-by: Sultan Alsawaf <sultan@kerneltoast.com>
>> Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
>> Co-developed-by: Svetoslav Stoilov <Svetoslav.Stoilov@amd.com>
>> Signed-off-by: Svetoslav Stoilov <Svetoslav.Stoilov@amd.com>
>> Signed-off-by: Bin Du <Bin.Du@amd.com>
>> ---
>> MAINTAINERS | 2 +
>> drivers/media/platform/amd/isp4/Makefile | 1 +
>> drivers/media/platform/amd/isp4/isp4.c | 10 +
>> drivers/media/platform/amd/isp4/isp4_subdev.c | 95 +-
>> drivers/media/platform/amd/isp4/isp4_subdev.h | 2 +
>> drivers/media/platform/amd/isp4/isp4_video.c | 1213 +++++++++++++++++
>> drivers/media/platform/amd/isp4/isp4_video.h | 87 ++
>> 7 files changed, 1406 insertions(+), 4 deletions(-)
>> create mode 100644 drivers/media/platform/amd/isp4/isp4_video.c
>> create mode 100644 drivers/media/platform/amd/isp4/isp4_video.h
>
> [snip]
>
>> diff --git a/drivers/media/platform/amd/isp4/isp4_video.c b/drivers/media/platform/amd/isp4/isp4_video.c
>> new file mode 100644
>> index 000000000000..642faff83287
>> --- /dev/null
>> +++ b/drivers/media/platform/amd/isp4/isp4_video.c
>
> [snip]
>
>> +static int isp4vid_ioctl_querycap(struct file *file, void *fh, struct v4l2_capability *cap)
>> +{
>> + struct isp4vid_dev *isp_vdev = video_drvdata(file);
>> +
>> + strscpy(cap->driver, ISP4VID_ISP_DRV_NAME, sizeof(cap->driver));
>> + snprintf(cap->card, sizeof(cap->card), "%s", ISP4VID_ISP_DRV_NAME);
>> + snprintf(cap->bus_info, sizeof(cap->bus_info),
>> + "platform:%s", ISP4VID_ISP_DRV_NAME);
>
> The bus_info is set by v4l_quercap, I think you can drop it here (please
> double-check the result).
>
Yes, you are definitely correct. bus_info is set by media_set_bus_info
call in v4l_querycap. Will drop it in the next version.
>> +
>> + cap->capabilities |= (V4L2_CAP_STREAMING |
>> + V4L2_CAP_VIDEO_CAPTURE | V4L2_CAP_IO_MC);
>
> You can now drop V4L2_CAP_IO_MC (and there's no need for parentheses).
>
Sure, will update in the next version.
>> +
>> + dev_dbg(isp_vdev->dev, "%s|capabilities=0x%X",
>> + isp_vdev->vdev.name, cap->capabilities);
>> +
>> + return 0;
>> +}
>
> [snip]
>
--
Regards,
Bin
next prev parent reply other threads:[~2025-09-05 7:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 10:08 [PATCH v3 1/7] media: platform: amd: Introduce amd isp4 capture driver Bin Du
2025-08-28 10:08 ` [PATCH v3 2/7] media: platform: amd: low level support for isp4 firmware Bin Du
2025-08-28 10:08 ` [PATCH v3 3/7] media: platform: amd: Add isp4 fw and hw interface Bin Du
2025-08-28 10:08 ` [PATCH v3 4/7] media: platform: amd: isp4 subdev and firmware loading handling added Bin Du
2025-09-02 7:48 ` Markus Elfring
2025-09-05 6:35 ` Du, Bin
2025-09-03 10:10 ` Laurent Pinchart
2025-08-28 10:08 ` [PATCH v3 5/7] media: platform: amd: isp4 video node and buffers " Bin Du
2025-09-02 8:10 ` Markus Elfring
2025-09-02 9:16 ` Du, Bin
2025-09-03 10:08 ` Laurent Pinchart
2025-09-05 7:05 ` Du, Bin [this message]
2025-08-28 10:08 ` [PATCH v3 6/7] media: platform: amd: isp4 debug fs logging and more descriptive errors Bin Du
2025-08-28 10:08 ` [PATCH v3 7/7] Documentation: add documentation of AMD isp 4 driver Bin Du
2025-08-28 16:50 ` Mario Limonciello
2025-09-02 3:04 ` Du, Bin
2025-09-03 10:04 ` Laurent Pinchart
2025-09-03 10:34 ` Du, Bin
2025-08-28 16:54 ` [PATCH v3 1/7] media: platform: amd: Introduce amd isp4 capture driver Mario Limonciello
2025-09-02 3:11 ` Du, Bin
2025-09-02 6:48 ` Sakari Ailus
2025-09-02 7:58 ` Sakari Ailus
2025-09-02 9:09 ` Du, Bin
2025-09-02 7:06 ` Markus Elfring
2025-09-02 9:05 ` Du, Bin
2025-09-02 12:49 ` Laurent Pinchart
2025-09-03 3:22 ` Du, Bin
2025-09-03 7:51 ` Laurent Pinchart
2025-09-03 8:20 ` Du, Bin
2025-09-10 17:17 ` Mario Limonciello
2025-09-11 2:19 ` Du, Bin
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=da070ae7-6347-4ce5-a0c1-11d1b0e491bf@amd.com \
--to=bin.du@amd.com \
--cc=Dominic.Antony@amd.com \
--cc=Phil.Jawich@amd.com \
--cc=anson.tsao@amd.com \
--cc=benjamin.chan@amd.com \
--cc=bryan.odonoghue@linaro.org \
--cc=gjorgji.rosikopulos@amd.com \
--cc=hverkuil@xs4all.nl \
--cc=king.li@amd.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mchehab@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=pratap.nirujogi@amd.com \
--cc=richard.gong@amd.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sultan@kerneltoast.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
all inboxes | Powered by JetHome®