From: Jonathan Cameron <jic23@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-iio@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Andre Werner <andre.werner@systec-electronic.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@denx.de>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Mark Brown <broonie@kernel.org>,
Naresh Solanki <naresh.solanki@9elements.com>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
Rob Herring <robh+dt@kernel.org>,
Stefan Windfeldt-Prytz <stefan.windfeldt-prytz@axis.com>,
Vincent Tremblay <vincent@vtremblay.dev>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 2/2] iio: light: isl76682: Add ISL76682 driver
Date: Sun, 26 Nov 2023 18:16:55 +0000 [thread overview]
Message-ID: <20231126181655.4e1040f9@jic23-huawei> (raw)
In-Reply-To: <20231125222738.97875-2-marex@denx.de>
On Sat, 25 Nov 2023 23:26:23 +0100
Marek Vasut <marex@denx.de> wrote:
> The ISL76682 is very basic ALS which only supports ALS or IR mode
> in four ranges, 1k/4k/16k/64k LUX. There is no IRQ support or any
> other fancy functionality.
>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
> Signed-off-by: Marek Vasut <marex@denx.de>
Hi Marek,
One last question + a comment in general. Act on that if you like.
Thanks,
Jonathan
> +static int integration_time_available[] = { 0, ISL76682_INT_TIME_US };
Why have an available attribute for a single value. Is it useful for anything?
> +static int isl76682_probe(struct i2c_client *client)
> +{
...
> + indio_dev->info = &isl76682_info;
> + indio_dev->channels = isl76682_channels;
> + indio_dev->num_channels = ARRAY_SIZE(isl76682_channels);
> + indio_dev->name = ISL76682_DRIVER_NAME;
Trivial but I'm not a fan of using defines in cases like this. It just makes
me go find the define when I could see the string directly here.
In cases where matching or similar strictly requires the naming to be the same
in various places a define is useful. In this case less so.
Anyhow, it's a very minor comment so never mind if you prefer to leave it
as it stands.
> + indio_dev->modes = INDIO_DIRECT_MODE;
> +
> + return devm_iio_device_register(dev, indio_dev);
> +}
next prev parent reply other threads:[~2023-11-26 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 22:26 [PATCH v5 1/2] dt-bindings: iio: light: isl76682: Document ISL76682 Marek Vasut
2023-11-25 22:26 ` [PATCH v5 2/2] iio: light: isl76682: Add ISL76682 driver Marek Vasut
2023-11-26 18:16 ` Jonathan Cameron [this message]
2023-11-26 22:09 ` Marek Vasut
2023-12-01 18:17 ` Jonathan Cameron
2023-12-02 6:48 ` Marek Vasut
2023-12-04 11:13 ` Jonathan Cameron
2023-11-26 19:33 ` Dr.-Ing. Andre Werner
2023-11-26 22:17 ` Marek Vasut
2023-12-01 18:20 ` Jonathan Cameron
2023-12-02 6:46 ` Marek Vasut
2023-11-27 16:11 ` Andy Shevchenko
2023-11-27 16:13 ` Andy Shevchenko
2023-11-27 20:52 ` Marek Vasut
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=20231126181655.4e1040f9@jic23-huawei \
--to=jic23@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=andre.werner@systec-electronic.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luca.ceresoli@bootlin.com \
--cc=marex@denx.de \
--cc=mazziesaccount@gmail.com \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=robh+dt@kernel.org \
--cc=stefan.windfeldt-prytz@axis.com \
--cc=vincent@vtremblay.dev \
/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).