Linux Media Controller development
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Benjamin MUGNIER <benjamin.mugnier@foss.st.com>
Cc: linux-media@vger.kernel.org, alain.volmat@foss.st.com,
	hugues.fruchet@foss.st.com, sylvain.petinot@foss.st.com,
	dave.stevenson@raspberrypi.com,
	laurent.pinchart@ideasonboard.com,
	kieran.bingham@ideasonboard.com, nicolas@ndufresne.ca,
	hverkuil@xs4all.nl
Subject: Re: [PATCH v6 4/4] media: i2c: Add driver for ST VGXY61 camera sensor
Date: Mon, 10 Oct 2022 08:29:37 +0000	[thread overview]
Message-ID: <Y0PX8SRn51FlOS5c@paasikivi.fi.intel.com> (raw)
In-Reply-To: <af876e81-9105-9a0f-4dd1-47bc17886536@foss.st.com>

Hi Benjamin,

On Fri, Oct 07, 2022 at 02:24:16PM +0200, Benjamin MUGNIER wrote:
> Hi Sakari,
> 
> Thank you for your review.
> Please consider everything not commented as queued for v7.
> 
> On 10/6/22 21:14, Sakari Ailus wrote:
> > Hi Benjamin,
> > 
> > Thanks for the update. A few more comments below...
> > 
> > On Tue, Sep 27, 2022 at 10:37:02AM +0200, Benjamin Mugnier wrote:
> >> +static const char * const vgxy61_hdr_mode_menu[] = {
> >> +	"HDR linearize",
> >> +	"HDR substraction",
> >> +	"No HDR",
> >> +};
> > 
> > I think more documentation is needed on the HDR modes. What do these mean?
> > For instance, are they something that requires further processing or is the
> > result e.g. a ready HDR image?
> > 
> > This should probably make it to driver specific documentation.
> > 
> 
> Sure, in fact I did something like this in v3:
> https://lore.kernel.org/linux-media/20220512074037.3829926-4-benjamin.mugnier@foss.st.com/
> 
> Since I standardized the control I was unsure what to do with this documentation, and dropped it.
> I will add back the Documentation/userspace-api/media/drivers/st-vgxy61.rst file from this commit to the patchset, while changing the control name to the new one.

Yes, please. That seems reasonably good.

I think Laurent's proposal on a HDR control for sensor-implemented HDR is a
good one. Further controls can be added later on.

> >> +	sensor->gpios_polarity = of_property_read_bool(dev->of_node,
> >> +						       "invert-gpios-polarity");

How about:

	device_property_read_bool(dev, ...);

> > 
> > I thought we did discuss dropping support for sensor synchronisation in
> > this version?
> > 
> 
> This properties affects strobing lights gpios polarities as you can see
> in vgxy61_update_gpios_strobe_polarity. If set to '1' all strobing gpios
> are inverted. This has nothing to do with the sensor synchronization.

So this is for strobing a LED flash? It would be good to mention this in
DT bindings.

> 
> Now I realize this is poorly named, and I even forgot to document it in
> the device tree bindings file. I apologize.

No problem.

> 
> I would like to rename it to 'st,strobe-polarity' since this is vendor
> specific and to better reflect that it affects strobing gpios. I'll make
> this change for v7 and document this in the bindings file too. Tell me if
> there is any issues with that.

That name seems reasonable to me. Although, *if* this is actually usable as
a GPIO as the bindings suggest, then the GPIO flags would probably be a
better alternative.

-- 
Kind regards,

Sakari Ailus

  parent reply	other threads:[~2022-10-10  8:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  8:36 [PATCH v6 0/4] media: Add ST VGXY61 camera sensor driver Benjamin Mugnier
2022-09-27  8:36 ` [PATCH v6 1/4] media: v4l: Add 1X16 16-bit greyscale media bus code definition Benjamin Mugnier
2022-10-06 21:26   ` Laurent Pinchart
2022-10-07 11:56     ` Benjamin MUGNIER
2022-09-27  8:37 ` [PATCH v6 2/4] media: v4l: ctrls: Add a control for HDR mode Benjamin Mugnier
2022-09-27  8:37 ` [PATCH v6 3/4] media: dt-bindings: media: i2c: Add ST VGXY61 camera sensor binding Benjamin Mugnier
2022-10-06 19:15   ` Sakari Ailus
2022-10-07 11:57     ` Benjamin MUGNIER
2022-10-07 12:28       ` Benjamin MUGNIER
2022-09-27  8:37 ` [PATCH v6 4/4] media: i2c: Add driver for ST VGXY61 camera sensor Benjamin Mugnier
2022-10-06 19:14   ` Sakari Ailus
2022-10-07 12:24     ` Benjamin MUGNIER
2022-10-07 12:32       ` Laurent Pinchart
2022-10-07 12:38         ` Benjamin MUGNIER
2022-10-07 13:19           ` Laurent Pinchart
2022-10-07 14:06             ` Benjamin MUGNIER
2022-10-10  8:29       ` Sakari Ailus [this message]
2022-10-10  9:19         ` Benjamin MUGNIER
2022-10-10  9:33           ` Sakari Ailus
2022-10-10  9:50             ` Benjamin MUGNIER
2022-10-10 11:55               ` Sakari Ailus
2022-10-10 12:11                 ` Benjamin MUGNIER
2022-10-10 12:52                   ` Sakari Ailus
2022-10-10 13:12                     ` Benjamin MUGNIER
2022-10-13  8:00                       ` Sakari Ailus
2022-10-18  7:54                         ` 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=Y0PX8SRn51FlOS5c@paasikivi.fi.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=alain.volmat@foss.st.com \
    --cc=benjamin.mugnier@foss.st.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=hugues.fruchet@foss.st.com \
    --cc=hverkuil@xs4all.nl \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=nicolas@ndufresne.ca \
    --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