[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a581b619-ecb7-4210-b025-9516d0fb0c64@amd.com>
Date: Wed, 3 Sep 2025 16:20:41 +0800
From: "Du, Bin" <bin.du@....com>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: mchehab@...nel.org, hverkuil@...all.nl, bryan.odonoghue@...aro.org,
sakari.ailus@...ux.intel.com, prabhakar.mahadev-lad.rj@...renesas.com,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
sultan@...neltoast.com, pratap.nirujogi@....com, benjamin.chan@....com,
king.li@....com, gjorgji.rosikopulos@....com, Phil.Jawich@....com,
Dominic.Antony@....com, mario.limonciello@....com, richard.gong@....com,
anson.tsao@....com, Svetoslav Stoilov <Svetoslav.Stoilov@....com>
Subject: Re: [PATCH v3 1/7] media: platform: amd: Introduce amd isp4 capture
driver
On 9/3/2025 3:51 PM, Laurent Pinchart wrote:
> On Wed, Sep 03, 2025 at 11:22:27AM +0800, Du, Bin wrote:
>> Thanks Laurent Pinchart
>>
>> On 9/2/2025 8:49 PM, Laurent Pinchart wrote:
>>> Hi Bin,
>>>
>>> Could you please provide the v4l2-compliance report (please use the
>>> very latest version of v4l2-compliance), as well as the output of
>>> `media-ctl -p -d /dev/media0` (replacing media0 with the appropriate
>>> device) ?
>>>
>>> Generally speaking, you should include a cover letter in patch series,
>>> and that information can be included in the cover letter.
>>>
>>
>> Yes, there is a cover letter for the patch series
>> https://lore.kernel.org/linux-media/20250828084507.94552-1-Bin.Du@amd.com/,
>> because of some server issue, the cover letter and left patches are sent
>> separately, really sorry for the confusing. It does contain
>> v4l2-compliance report, but the media-ctl output is missing, many thanks
>> for the guide, will include it either in the next patch
>
> My bad, I even replied to that cover letter, but then forgot about it.
>
Never mind, considering you have hundreds of mails, :)
>>> On Thu, Aug 28, 2025 at 06:08:05PM +0800, Bin Du wrote:
>>>> AMD isp4 capture is a v4l2 media device which implements media controller
>>>> interface. It has one sub-device (AMD ISP4 sub-device) endpoint which can
>>>> be connected to a remote CSI2 TX endpoint. It supports only one physical
>>>> interface for now. Also add ISP4 driver related entry info into the
>>>> MAINTAINERS file
>>>>
>>>> Co-developed-by: Svetoslav Stoilov <Svetoslav.Stoilov@....com>
>>>> Signed-off-by: Svetoslav Stoilov <Svetoslav.Stoilov@....com>
>>>> Signed-off-by: Bin Du <Bin.Du@....com>
>>>> ---
>>>> MAINTAINERS | 13 +++
>>>> drivers/media/platform/Kconfig | 1 +
>>>> drivers/media/platform/Makefile | 1 +
>>>> drivers/media/platform/amd/Kconfig | 3 +
>>>> drivers/media/platform/amd/Makefile | 3 +
>>>> drivers/media/platform/amd/isp4/Kconfig | 13 +++
>>>> drivers/media/platform/amd/isp4/Makefile | 6 ++
>>>> drivers/media/platform/amd/isp4/isp4.c | 121 +++++++++++++++++++++++
>>>> drivers/media/platform/amd/isp4/isp4.h | 24 +++++
>>>> 9 files changed, 185 insertions(+)
>>>> create mode 100644 drivers/media/platform/amd/Kconfig
>>>> create mode 100644 drivers/media/platform/amd/Makefile
>>>> create mode 100644 drivers/media/platform/amd/isp4/Kconfig
>>>> create mode 100644 drivers/media/platform/amd/isp4/Makefile
>>>> create mode 100644 drivers/media/platform/amd/isp4/isp4.c
>>>> create mode 100644 drivers/media/platform/amd/isp4/isp4.h
>
--
Regards,
Bin
Powered by blists - more mailing lists