From: Andreas Klinger <ak@it-klinger.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
lars@metafoo.de, javier.carrasco.cruz@gmail.com,
mazziesaccount@gmail.com, andriy.shevchenko@linux.intel.com,
muditsharma.info@gmail.com, perdaniel.olsson@axis.com,
emil.gedenryd@axis.com, mgonellabolduc@dimonoff.com,
arthur.becker@sentec.com, clamor95@gmail.com,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/3] iio: light: add support for veml6046x00 RGBIR color sensor
Date: Sun, 18 May 2025 10:21:05 +0200 [thread overview]
Message-ID: <aCmYcTxRYDbYMo3H@mail.your-server.de> (raw)
In-Reply-To: <20250515173728.1eaebd5c@jic23-huawei>
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
Hi Jonathan,
thanks for the review.
Jonathan Cameron <jic23@kernel.org> schrieb am Do, 15. Mai 17:37:
> > +/*
> > + * Factors for lux / raw count in dependency of integration time (IT) as rows
> > + * and driver gain in columns
> > + * Columns:
> > + * x0.25 x0.33 x0.5 x0.66 x1 x2
> > + * Rows:
> > + * 3.125 6.25 12.5 25 50 100 200 400ms
> > + */
> > +static const u32 veml6046x00_it_gains[][6][2] = {
> > +{{5, 376000}, {4, 72700}, {2, 688000}, {2, 36400}, {1, 344000}, {0, 672000}},
> > +{{2, 688000}, {2, 36350}, {1, 344000}, {1, 18200}, {0, 672000}, {0, 336000}},
> > +{{1, 344000}, {1, 18175}, {0, 672000}, {0, 509100}, {0, 336000}, {0, 168000}},
> > +{{0, 672000}, {0, 509087}, {0, 336000}, {0, 254550}, {0, 168000}, {0, 84000}},
> > +{{0, 336000}, {0, 254543}, {0, 168000}, {0, 127275}, {0, 84000}, {0, 42000}},
> > +{{0, 168000}, {0, 127271}, {0, 84000}, {0, 63637}, {0, 42000}, {0, 21000}},
> > +{{0, 84000}, {0, 63635}, {0, 42000}, {0, 31818}, {0, 21000}, {0, 10500}},
> > +{{0, 42000}, {0, 31817}, {0, 21000}, {0, 15909}, {0, 10500}, {0, 5250}},
> I'd prefer
> { { 0, 42000 }, { 0, 31817 }, etc for this formatting.
> Don't worry about going a little over 80 chars to do so - I think the readability
> makes it worth while.
I tried it and ended up with 101 characters in a line. I'll pick up the
suggestion of Andy for the next version.
Andreas
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-05-18 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 20:23 [PATCH v3 0/3] iio:light: add driver for veml6046x00 RGBIR color sensor Andreas Klinger
2025-05-05 20:23 ` [PATCH v3 1/3] dt-bindings: iio: light: veml6046x00: add " Andreas Klinger
2025-05-05 20:23 ` [PATCH v3 2/3] iio: light: add support for veml6046x00 RGBIR " Andreas Klinger
2025-05-08 19:58 ` Andy Shevchenko
2025-05-15 16:37 ` Jonathan Cameron
2025-05-18 8:21 ` Andreas Klinger [this message]
2025-05-05 20:23 ` [PATCH v3 3/3] MAINTAINER: add maintainer for veml6046x00 Andreas Klinger
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=aCmYcTxRYDbYMo3H@mail.your-server.de \
--to=ak@it-klinger.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arthur.becker@sentec.com \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emil.gedenryd@axis.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--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=mgonellabolduc@dimonoff.com \
--cc=muditsharma.info@gmail.com \
--cc=perdaniel.olsson@axis.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