public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Changhuang Liang <changhuang.liang@starfivetech.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Ming Qian <ming.qian@nxp.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Nicolas Dufresne <nicolas.dufresne@collabora.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>,
	Mingjia Zhang <mingjia.zhang@mediatek.com>
Cc: Jack Zhu <jack.zhu@starfivetech.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev
Subject: Re: [PATCH v3 00/13] Add ISP 3A for StarFive
Date: Mon, 12 Feb 2024 13:40:57 +0100	[thread overview]
Message-ID: <5940e2cd-64f9-45d6-9e1d-e9a1d14c8ad9@gmail.com> (raw)
In-Reply-To: <20240205090424.40302-1-changhuang.liang@starfivetech.com>

Dear Changhuang,

On 05/02/2024 10:04, Changhuang Liang wrote:
> Changhuang Liang (13):
>    media: starfive: Add JH7110 ISP module definitions
>    media: Documentation: Add description for StarFive ISP metadata
>      formats
>    media: videodev2.h, v4l2-ioctl: Add StarFive ISP meta buffer format
>    staging: media: starfive: Add a params sink pad and a scd source pad
>      for ISP
>    staging: media: starfive: Separate buffer from ISP hardware operation
>    staging: media: starfive: Separate buffer be a common file
>    staging: media: starfive: Separate ISP hardware from capture device
>    staging: media: starfive: Add for StarFive ISP 3A SC
>    staging: media: starfive: Update ISP initialise config for 3A
>    staging: media: starfive: Add V4L2_CAP_IO_MC capability
>    staging: media: starfive: Add ISP params video device
>    staging: media: starfive: Add ISP parameters hardware configure
>    admin-guide: media: Update documents for StarFive Camera Subsystem

I think instead of adding more support on top of the staging driver, the first 
step would be to get the driver out of staging and make it a regular Linux 
driver. After that new HW support should be added.

Regards,
Matthias

  parent reply	other threads:[~2024-02-12 12:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05  9:04 [PATCH v3 00/13] Add ISP 3A for StarFive Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 01/13] media: starfive: Add JH7110 ISP module definitions Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 02/13] media: Documentation: Add description for StarFive ISP metadata formats Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 03/13] media: videodev2.h, v4l2-ioctl: Add StarFive ISP meta buffer format Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 04/13] staging: media: starfive: Add a params sink pad and a scd source pad for ISP Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 05/13] staging: media: starfive: Separate buffer from ISP hardware operation Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 06/13] staging: media: starfive: Separate buffer be a common file Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 07/13] staging: media: starfive: Separate ISP hardware from capture device Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 08/13] staging: media: starfive: Add for StarFive ISP 3A SC Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 09/13] staging: media: starfive: Update ISP initialise config for 3A Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 10/13] staging: media: starfive: Add V4L2_CAP_IO_MC capability Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 11/13] staging: media: starfive: Add ISP params video device Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 12/13] staging: media: starfive: Add ISP parameters hardware configure Changhuang Liang
2024-02-05  9:04 ` [PATCH v3 13/13] admin-guide: media: Update documents for StarFive Camera Subsystem Changhuang Liang
2024-02-12 12:40 ` Matthias Brugger [this message]
2024-02-12 16:33   ` [PATCH v3 00/13] Add ISP 3A for StarFive Laurent Pinchart
2024-03-06  2:19 ` 回复: " Changhuang Liang

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=5940e2cd-64f9-45d6-9e1d-e9a1d14c8ad9@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=changhuang.liang@starfivetech.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jack.zhu@starfivetech.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=ming.qian@nxp.com \
    --cc=mingjia.zhang@mediatek.com \
    --cc=nicolas.dufresne@collabora.com \
    --cc=tomi.valkeinen+renesas@ideasonboard.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