public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jack Zhu <jack.zhu@starfivetech.com>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
	bryan.odonoghue@linaro.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-staging@lists.linux.dev,
	changhuang.liang@starfivetech.com
Subject: Re: [PATCH v10 0/8] Add StarFive Camera Subsystem driver
Date: Wed, 18 Oct 2023 14:49:19 +0300	[thread overview]
Message-ID: <20231018114919.GF11118@pendragon.ideasonboard.com> (raw)
In-Reply-To: <c255e215-b1ed-7397-0534-8d6ebda86350@starfivetech.com>

On Wed, Oct 18, 2023 at 11:11:40AM +0800, Jack Zhu wrote:
> On 2023/10/16 19:40, Hans Verkuil wrote:
> > On 08/10/2023 10:51, Jack Zhu wrote:
> >> Hi,
> >> 
> >> This series is the v10 series that attempts to support the Camera Subsystem
> >> found on StarFive JH7110 SoC.
> >> 
> >> This series is based on top of the master branch of media_stage repository,
> >> which is tested with a v4l2-compliance compiled from the git repo
> >> (git://linuxtv.org/v4l-utils.git).
> > 
> > I get one smatch warning:
> > 
> > drivers/staging/media/starfive/camss/stf-isp.c:122 isp_enum_mbus_code() warn: unsigned 'code->index' is never less than zero.
> 
> Could you please tell me the code check command? This way I can use it to check
> my next commit.
> 
> > And I also notice that there is no TODO file: staging drivers should have a
> > TODO file explaining what needs to be done to get them out of staging.
> 
> OK, I'll add it to my next commit. I previously misunderstood that it was submitted
> when moving out of staging.
> 
> > I'm curious to know that as well :-)
> > 
> > It looks like there is a lot of additional development that can be done, since
> > most of the ISP parameters appear to be hardcoded.
> 
> Part is the module initialization configuration. In the next stage, we will use
> incremental development to implement 3A functions.

I'm really looking forward to that part :-)

-- 
Regards,

Laurent Pinchart

      parent reply	other threads:[~2023-10-18 11:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-08  8:51 [PATCH v10 0/8] Add StarFive Camera Subsystem driver Jack Zhu
2023-10-08  8:51 ` [PATCH v10 1/8] media: dt-bindings: Add JH7110 Camera Subsystem Jack Zhu
2023-10-08  8:51 ` [PATCH v10 2/8] media: admin-guide: Add starfive_camss.rst for Starfive " Jack Zhu
2023-10-08  8:51 ` [PATCH v10 3/8] media: staging: media: starfive: camss: Add core driver Jack Zhu
2023-10-08  8:51 ` [PATCH v10 4/8] media: staging: media: starfive: camss: Add video driver Jack Zhu
2023-10-08  8:51 ` [PATCH v10 5/8] media: staging: media: starfive: camss: Add ISP driver Jack Zhu
2023-10-08  8:51 ` [PATCH v10 6/8] media: staging: media: starfive: camss: Add capture driver Jack Zhu
2023-10-08  8:51 ` [PATCH v10 7/8] media: staging: media: starfive: camss: Add interrupt handling Jack Zhu
2023-10-08  8:51 ` [PATCH v10 8/8] media: staging: media: starfive: camss: Register devices Jack Zhu
2023-10-16 10:09 ` [PATCH v10 0/8] Add StarFive Camera Subsystem driver Jack Zhu
2023-10-16 11:40 ` Hans Verkuil
2023-10-18  2:37   ` Jack Zhu
2023-10-18  8:48     ` Jack Zhu
2023-10-18  8:50     ` Hans Verkuil
2023-10-18  9:25       ` Jack Zhu
2023-10-18  9:31         ` Hans Verkuil
2023-10-18  9:52           ` Jack Zhu
2023-10-18  9:56             ` Hans Verkuil
2023-10-19  9:02               ` Hans Verkuil
2023-10-18  3:11   ` Jack Zhu
2023-10-18  7:12     ` Hans Verkuil
2023-10-18 11:49     ` Laurent Pinchart [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=20231018114919.GF11118@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=changhuang.liang@starfivetech.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jack.zhu@starfivetech.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@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=rfoss@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=todor.too@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