From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Okan Sahin <okan.sahin@analog.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Caleb Connolly <caleb.connolly@linaro.org>,
Marcus Folkesson <marcus.folkesson@gmail.com>,
Ramona Bolboaca <ramona.bolboaca@analog.com>,
ChiYuan Huang <cy_huang@richtek.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
William Breathitt Gray <william.gray@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v4 3/5] drivers: iio: adc: Add ADI MAX77541 ADC Support
Date: Thu, 2 Feb 2023 15:37:31 +0200 [thread overview]
Message-ID: <Y9u8m3EHux2b5Gip@smile.fi.intel.com> (raw)
In-Reply-To: <20230201103534.108136-4-okan.sahin@analog.com>
On Wed, Feb 01, 2023 at 01:35:16PM +0300, Okan Sahin wrote:
> The MAX77541 has an 8-bit Successive Approximation Register (SAR) ADC
> with four multiplexers for supporting the telemetry feature.
...
> +struct max77541_adc_iio {
> + struct regmap *regmap;
> +};
Is it really needed? See below.
...
> +enum max77541_adc_channel {
> + MAX77541_ADC_VSYS_V = 0,
0 is the default in C enums, why do you need this explicitly? If these are
HW related, you need to assign them all to be crystal clear.
> + MAX77541_ADC_VOUT1_V,
> + MAX77541_ADC_VOUT2_V,
> + MAX77541_ADC_TEMP,
> +};
...
> + reg_val = FIELD_GET(MAX77541_BITS_MX_CFG1_RNG, reg_val);
> +
Redundant blank line.
> + switch (reg_val) {
> + case LOW_RANGE:
> + *val = 6;
> + *val2 = 250000;
> + break;
> + case MID_RANGE:
> + *val = 12;
> + *val2 = 500000;
> + break;
> + case HIGH_RANGE:
> + *val = 25;
> + return IIO_VAL_INT;
> + default:
> + return -EINVAL;
> + }
...
struct regmap **regmap;
> + indio_dev = devm_iio_device_alloc(dev, sizeof(*info));
sizeof(*regmap)
> + if (!indio_dev)
> + return -ENOMEM;
> + info = iio_priv(indio_dev);
regmap = iio_priv(...);
> + info->regmap = dev_get_regmap(dev->parent, NULL);
*regmap = ...;
It won't probably gain anything in the code generation or memory footprint,
so up to you. But in general depending on API it might be a benefit.
...
> +static const struct platform_device_id max77541_adc_platform_id[] = {
> + { "max77541-adc", },
Inner comma is not needed.
> + { /* sentinel */ }
> +};
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-02-02 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 10:35 [PATCH v4 0/5] Add MAX77541/MAX77540 PMIC Support Okan Sahin
2023-02-01 10:35 ` [PATCH v4 1/5] dt-bindings: regulator: Add ADI MAX77541/MAX77540 Regulator Okan Sahin
2023-02-01 14:46 ` Krzysztof Kozlowski
2023-02-01 10:35 ` [PATCH v4 2/5] drivers: regulator: Add ADI MAX77541/MAX77540 Regulator Support Okan Sahin
2023-02-01 14:30 ` Mark Brown
2023-02-20 14:58 ` Sahin, Okan
2023-02-20 15:30 ` Andy Shevchenko
2023-02-02 13:30 ` Andy Shevchenko
2023-02-01 10:35 ` [PATCH v4 3/5] drivers: iio: adc: Add ADI MAX77541 ADC Support Okan Sahin
2023-02-01 14:44 ` Krzysztof Kozlowski
2023-02-02 13:37 ` Andy Shevchenko [this message]
2023-02-01 10:35 ` [PATCH v4 4/5] dt-bindings: mfd: Add ADI MAX77541/MAX77540 Okan Sahin
2023-02-01 14:47 ` Krzysztof Kozlowski
2023-02-01 10:35 ` [PATCH v4 5/5] drivers: mfd: Add ADI MAX77541/MAX77540 PMIC Support Okan Sahin
2023-03-03 13:29 ` Lee Jones
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=Y9u8m3EHux2b5Gip@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=broonie@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=okan.sahin@analog.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=ramona.bolboaca@analog.com \
--cc=robh+dt@kernel.org \
--cc=william.gray@linaro.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