public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Benjamin Mugnier <benjamin.mugnier@foss.st.com>,
	Nicolas Dufresne <nicolas@ndufresne.ca>,
	linux-media@vger.kernel.org, alain.volmat@foss.st.com,
	hugues.fruchet@foss.st.com, sylvain.petinot@foss.st.com,
	dave.stevenson@raspberrypi.com, sakari.ailus@linux.intel.com,
	kieran.bingham@ideasonboard.com, linux-hwmon@vger.kernel.org,
	Ricardo Ribalda <ribalda@chromium.org>
Subject: Re: [PATCH v2 2/5] media: v4l: ctrls: Add a control for temperature
Date: Wed, 20 Apr 2022 19:51:41 +0300	[thread overview]
Message-ID: <YmA6HbHybCkhTYFH@pendragon.ideasonboard.com> (raw)
In-Reply-To: <57bb64db-9273-0e52-cf6d-0c7ff172ddde@roeck-us.net>

On Wed, Apr 20, 2022 at 09:19:53AM -0700, Guenter Roeck wrote:
> On 4/20/22 08:19, Benjamin Mugnier wrote:
> [ ... ]
> >>
> >> It's the two most common use cases for imaging sensor temperature
> >> measurements that I know of. My question to Benjamin is if he has the
> >> same and/or other use cases.
> >>
> > 
> > Just like you said in a previous mail. This temperature sensor can
> > be used to implement a retroactive loop from the host according to
> > its value, such as noise correction for instance.
> > We don't have anything in the Linux user space that implements this
> > yet, this was in anticipation.
> > So dropping it is fine, I will come back to it if need be ;)
> 
> When you implement this in userspace, you might want to consider situations
> where the temperature is _not_ reported via media controls (which might
> at least in theory happen if the temperature sensor is not part of the
> v4l device), or for existing drivers with hwmon support
> (drivers/media/i2c/video-i2c.c comes into mind).

That's a good point. I wouldn't expect external temperature sensors to
be very useful for this use case though, as what we really need is the
temperature of the camera sensor die.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2022-04-20 16:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 11:18 [PATCH v2 0/5] media: Add ST VGXY61 camera sensor driver Benjamin Mugnier
2022-04-15 11:18 ` [PATCH v2 1/5] media: v4l: Add 1X16 16-bit greyscale media bus code definition Benjamin Mugnier
2022-04-15 14:47   ` Laurent Pinchart
2022-04-15 11:18 ` [PATCH v2 2/5] media: v4l: ctrls: Add a control for temperature Benjamin Mugnier
2022-04-15 14:37   ` Laurent Pinchart
2022-04-20 13:01     ` Benjamin Mugnier
2022-04-19  7:03   ` Hans Verkuil
2022-04-20 13:01     ` Benjamin Mugnier
2022-04-19 18:24   ` Nicolas Dufresne
2022-04-19 19:28     ` Guenter Roeck
2022-04-19 21:01       ` Laurent Pinchart
2022-04-19 22:04         ` Guenter Roeck
2022-04-20 13:01           ` Benjamin Mugnier
2022-04-20 13:21             ` Laurent Pinchart
2022-04-20 13:58               ` Guenter Roeck
2022-04-20 14:23                 ` Laurent Pinchart
2022-04-20 15:19                   ` Benjamin Mugnier
2022-04-20 16:19                     ` Guenter Roeck
2022-04-20 16:51                       ` Laurent Pinchart [this message]
2022-04-15 11:18 ` [PATCH v2 3/5] media: v4l: ctrls: Add user control base for st-vgxy61 controls Benjamin Mugnier
2022-04-15 14:51   ` Laurent Pinchart
2022-04-15 11:18 ` [PATCH v2 4/5] media: dt-bindings: media: i2c: Add ST VGXY61 camera sensor binding Benjamin Mugnier
2022-04-15 14:59   ` Laurent Pinchart
2022-04-20 13:01     ` Benjamin Mugnier
2022-04-15 11:18 ` [PATCH v2 5/5] media: i2c: Add driver for ST VGXY61 camera sensor Benjamin Mugnier
2022-04-15 15:39   ` Laurent Pinchart
2022-04-20 13:01     ` Benjamin Mugnier
2022-04-20 16:48       ` Laurent Pinchart
2022-04-22  8:44         ` Benjamin Mugnier
2022-04-22 13:29           ` Laurent Pinchart
2022-04-22 14:40             ` Benjamin Mugnier
2022-04-24 16:34               ` Laurent Pinchart
2022-04-27 14:27                 ` 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=YmA6HbHybCkhTYFH@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.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=kieran.bingham@ideasonboard.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=nicolas@ndufresne.ca \
    --cc=ribalda@chromium.org \
    --cc=sakari.ailus@linux.intel.com \
    --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