From: Jonathan Cameron <jic23@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Mudit Sharma <muditsharma.info@gmail.com>,
lars@metafoo.de, krzk+dt@kernel.org, conor+dt@kernel.org,
robh@kernel.org, ivan.orlov0322@gmail.com,
javier.carrasco.cruz@gmail.com, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org, "Haikola,
Heikki" <Heikki.Haikola@fi.rohmeurope.com>,
"Mutanen, Mikko" <Mikko.Mutanen@fi.rohmeurope.com>
Subject: Re: [PATCH v4 2/2] iio: light: ROHM BH1745 colour sensor
Date: Sun, 23 Jun 2024 17:52:16 +0100 [thread overview]
Message-ID: <20240623175216.6bb09390@jic23-huawei> (raw)
In-Reply-To: <6e5d6734-eae0-49fd-a1ed-beda00e37209@gmail.com>
> > Gut feeling is normally people are actually cranking scaling of light
> > channels up and down together as hopefully they are approximately balanced
> > for 'white' giving similar scales on all sensors (by filters or fixed gains)
>
> I appreciate your insight on how people usually use these devices :)
> It's very valuable to me.
Pah, never trust me on this stuff. I've not been on the 'ground' with
real sensor for a long time and even then my use cases were far from typical.
These days I just play with big toys (though having just helped moved them
between buildings this week I can say that they are at least real and not all
in the cloud).
>
> > and people would only need to care if they were trying to measure a weak
> > blue signal in a red world. If we have a case that doesn't work well
> > for that sort of global scaling (I can sort of see that as a possible
> > problem due to the transition states not being possible) then we
> > should make sure that one works!
>
> Yes. I think some users will eventually hit to a scale transition which
> will be NACKed by the driver. Also, I don't think this problem will be
> specific to the BU27034 sensor, but in some form this will be possible
> for many gain-time-scale type devices. I just don't have a good generic
> solution in my mind right now.
>
> Oh, besides, it seems raining stopped. Time to turn off my computer and
> go out to the yard :)
Wise!
>
> Yours,
> -- Matti
>
next prev parent reply other threads:[~2024-06-23 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 16:29 [PATCH v4 1/2] dt-bindings: iio: light: ROHM BH1745 Mudit Sharma
2024-06-06 16:29 ` [PATCH v4 2/2] iio: light: ROHM BH1745 colour sensor Mudit Sharma
2024-06-08 16:22 ` Jonathan Cameron
2024-06-10 5:58 ` Matti Vaittinen
2024-06-11 17:14 ` Jonathan Cameron
2024-06-12 6:07 ` Matti Vaittinen
2024-06-15 18:23 ` Jonathan Cameron
2024-06-17 7:08 ` Matti Vaittinen
2024-06-23 16:52 ` Jonathan Cameron [this message]
2024-06-17 18:52 ` Mudit Sharma
2024-06-17 18:47 ` Mudit Sharma
2024-06-08 15:27 ` [PATCH v4 1/2] dt-bindings: iio: light: ROHM BH1745 Jonathan Cameron
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=20240623175216.6bb09390@jic23-huawei \
--to=jic23@kernel.org \
--cc=Heikki.Haikola@fi.rohmeurope.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=Mikko.Mutanen@fi.rohmeurope.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ivan.orlov0322@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=muditsharma.info@gmail.com \
--cc=robh@kernel.org \
/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).