linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Benjamin Mugnier <benjamin.mugnier@foss.st.com>,
	Sylvain Petinot <sylvain.petinot@foss.st.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] media: i2c: Add driver for ST VD55G1 camera sensor
Date: Wed, 23 Apr 2025 15:48:12 +0000	[thread overview]
Message-ID: <aAkLvCqsJ9Tf-O2d@kekkonen.localdomain> (raw)
In-Reply-To: <20250422150746.GA23173@pendragon.ideasonboard.com>

Hi Laurent,

On Tue, Apr 22, 2025 at 06:07:46PM +0300, Laurent Pinchart wrote:
> Hi Benjamin,
> 
> Thank you for the patch.
> 
> On Fri, Apr 04, 2025 at 04:50:52PM +0200, Benjamin Mugnier wrote:
> > The VD55G1 is a monochrome global shutter camera with a 804x704 maximum
> > resolution with RAW8 and RAW10 bytes per pixel.
> > The driver supports :
> > - Auto exposure from the sensor, or manual exposure mode
> > - HDR subtraction mode, allowing edge detection and background removal
> > - Auto exposure cold start, using configuration values from last stream
> > to start the next one
> > - LED GPIOs for illumination
> > - Most standard camera sensor features (hblank, vblank, test patterns,
> > again, dgain, hflip, vflip, auto exposure bias, etc.)
> > Add driver source code to MAINTAINERS file.
> > 
> > Signed-off-by: Benjamin Mugnier <benjamin.mugnier@foss.st.com>
> > ---
> >  MAINTAINERS                |    2 +
> >  drivers/media/i2c/Kconfig  |   11 +
> >  drivers/media/i2c/Makefile |    1 +
> >  drivers/media/i2c/vd55g1.c | 2005 ++++++++++++++++++++++++++++++++++++++++++++
> >  4 files changed, 2019 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 4f5e9005063a157de69e81b10f8def9da9e6c04c..9991c5f63e3d49a4e7a6ef0071f3b81825e84eee 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -22416,6 +22416,7 @@ M:	Sylvain Petinot <sylvain.petinot@foss.st.com>
> >  L:	linux-media@vger.kernel.org
> >  S:	Maintained
> >  F:	Documentation/devicetree/bindings/media/i2c/st,vd55g1.yaml
> > +F:	drivers/media/i2c/vd55g1.c
> >  
> >  ST VGXY61 DRIVER
> >  M:	Benjamin Mugnier <benjamin.mugnier@foss.st.com>
> > @@ -24801,6 +24802,7 @@ F:	drivers/media/i2c/mt*
> >  F:	drivers/media/i2c/og*
> >  F:	drivers/media/i2c/ov*
> >  F:	drivers/media/i2c/s5*
> > +F:	drivers/media/i2c/vd55g1.c
> >  F:	drivers/media/i2c/vgxy61.c
> 
> I suppose that
> 
> F:	drivers/media/i2c/v*
> 
> would be too broad. Sakari, is it time to create a sensors subdirectory
> (not as a prerequisite for this series of course) ?

Good question. Right now everything is arranged according to the bus the
device attaches to, and camera sensors are practically all I²C devices. I
do anticipate to get some I3C devices in the future, but it's been slow.

Would you create a new directory for cameras under i2c? Should the same be
done to various bridge chips, TV tuners and the few flash controller
drivers we have left?

I don't have much of an opinion on this right now. While the current
arrangement requires some care when changing MAINTAINERS, it works for me.

-- 
Regards,

Sakari Ailus

  reply	other threads:[~2025-04-23 15:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 14:50 [PATCH v5 0/2] media: Add support for ST VD55G1 camera sensor Benjamin Mugnier
2025-04-04 14:50 ` [PATCH v5 1/2] media: dt-bindings: Add " Benjamin Mugnier
2025-04-22 13:11   ` Laurent Pinchart
2025-04-23 14:47     ` Benjamin Mugnier
2025-04-04 14:50 ` [PATCH v5 2/2] media: i2c: Add driver for " Benjamin Mugnier
2025-04-04 16:09   ` Christophe JAILLET
2025-04-07  9:07     ` Benjamin Mugnier
2025-04-07 19:59       ` Christophe JAILLET
2025-04-22 15:07   ` Laurent Pinchart
2025-04-23 15:48     ` Sakari Ailus [this message]
2025-04-29 11:06     ` Benjamin Mugnier

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=aAkLvCqsJ9Tf-O2d@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=benjamin.mugnier@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh@kernel.org \
    --cc=sylvain.petinot@foss.st.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;
as well as URLs for NNTP newsgroup(s).