public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: "Herve Codina (Schneider Electric)" <herve.codina@bootlin.com>
Cc: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	linux-iio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Pascal Eberhard" <pascal.eberhard@se.com>,
	"Miquel Raynal" <miquel.raynal@bootlin.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2 2/4] iio: adc: Add support for the Renesas RZ/N1 ADC
Date: Thu, 30 Oct 2025 11:00:12 +0200	[thread overview]
Message-ID: <aQMpHDwCqcrNrnT9@smile.fi.intel.com> (raw)
In-Reply-To: <20251029144644.667561-3-herve.codina@bootlin.com>

On Wed, Oct 29, 2025 at 03:46:42PM +0100, Herve Codina (Schneider Electric) wrote:
> The Renesas RZ/N1 ADC controller is the ADC controller available in the
> Renesas RZ/N1 SoCs family. It can use up to two internal ADC cores (ADC1
> and ADC2) those internal cores are not directly accessed but are handled
> through ADC controller virtual channels.

Looks much better, thanks! My comments below.

...

+ array_size,h

> +#include <linux/bitfield.h>
> +#include <linux/bits.h>
> +#include <linux/cleanup.h>
> +#include <linux/clk.h>

+ dev_printk.h
+ err.h

> +#include <linux/iio/iio.h>
> +#include <linux/io.h>
> +#include <linux/iopoll.h>
> +#include <linux/mod_devicetable.h>
> +#include <linux/module.h>

+ mutex.h

> +#include <linux/platform_device.h>
> +#include <linux/pm_runtime.h>
> +#include <linux/regulator/consumer.h>

+ types.h

...

> +#define RZN1_ADC_CONTROL_REG			0x2c

I would go with fixed-width values, e.g., 0x02c for the register definitions.

> +#define RZN1_ADC_CONTROL_ADC_BUSY		BIT(6)
> +
> +#define RZN1_ADC_FORCE_REG			0x30
> +#define RZN1_ADC_SET_FORCE_REG			0x34
> +#define RZN1_ADC_CLEAR_FORCE_REG		0x38

> +#define RZN1_ADC_CONFIG_REG			0x40

> +
> +#define RZN1_ADC_VC_REG(_n)			(0xc0 + 4 * (_n))

> +#define RZN1_ADC_ADC1_DATA_REG(_n)		(0x100 + 4 * (_n))
> +#define RZN1_ADC_ADC2_DATA_REG(_n)		(0x140 + 4 * (_n))

...

> +static int rzn1_adc_get_vref_mv(struct rzn1_adc *rzn1_adc, unsigned int chan)
> +{
> +	/*
> +	 * chan 0..7 use ADC1 ch 0..7. Vref related to ADC1 core
> +	 * chan 8..15 use ADC2 ch 0..7. Vref related to ADC2 core
> +	 */

Split it to two one line comments per each conditional.

> +	if (chan < 8)
> +		return rzn1_adc->adc1_vref_mv;
> +	else if (chan < 16)

Redundant 'else'.

> +		return rzn1_adc->adc2_vref_mv;
> +
> +	return -EINVAL;
> +}

...

> +static int rzn1_adc_read_raw(struct iio_dev *indio_dev, struct iio_chan_spec const *chan,
> +			     int *val, int *val2, long mask)
> +{
> +	struct rzn1_adc *rzn1_adc = iio_priv(indio_dev);
> +	int ret;
> +
> +	switch (mask) {
> +	case IIO_CHAN_INFO_RAW:
> +		ret = rzn1_adc_read_raw_ch(rzn1_adc, chan->channel, val);
> +		if (ret)
> +			return ret;
> +		return IIO_VAL_INT;
> +
> +	case IIO_CHAN_INFO_SCALE:
> +		ret = rzn1_adc_get_vref_mv(rzn1_adc, chan->channel);
> +		if (ret < 0)
> +			return ret;
> +		*val = ret;
> +		*val2 = 12;
> +		return IIO_VAL_FRACTIONAL_LOG2;

> +	default:
> +		break;
> +	}
> +
> +	return -EINVAL;

	default:
		return -EINVAL;

> +}

...

> +static const struct iio_info rzn1_adc_info = {
> +	.read_raw = &rzn1_adc_read_raw

Leave trailing comma, this is not a terminator entry.

> +};

...

> +	if (rzn1_adc->adc1_vref_mv >= 0) {

Can we call it _mV?

...

> +	if (rzn1_adc->adc2_vref_mv >= 0) {

Ditto.


...

> +	ret = devm_regulator_get_enable_optional(dev, avdd_name);
> +	if (ret < 0) {
> +		if (ret != -ENODEV)
> +			return dev_err_probe(dev, ret,
> +					     "Failed to get '%s' regulator\n",
> +					     avdd_name);
> +		return 0;
> +	}

	if (ret == -ENODEV)
		return dev_err_probe(); // takes less LoCs
	if (ret < 0) // do we need ' < 0' part?
		return 0;

> +	ret = devm_regulator_get_enable_read_voltage(dev, vref_name);
> +	if (ret < 0) {
> +		if (ret != -ENODEV)
> +			return dev_err_probe(dev, ret,
> +					     "Failed to get '%s' regulator\n",
> +					     vref_name);
> +		return 0;
> +	}

In the same way as above.

...

> +static DEFINE_RUNTIME_DEV_PM_OPS(rzn1_adc_pm_ops,
> +				 rzn1_adc_pm_runtime_suspend,
> +				 rzn1_adc_pm_runtime_resume, NULL);

Please, split it based on logic:

static DEFINE_RUNTIME_DEV_PM_OPS(rzn1_adc_pm_ops,
				 rzn1_adc_pm_runtime_suspend, rzn1_adc_pm_runtime_resume, NULL);

OR

static DEFINE_RUNTIME_DEV_PM_OPS(rzn1_adc_pm_ops,
				 rzn1_adc_pm_runtime_suspend,
				 rzn1_adc_pm_runtime_resume,
				 NULL);

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-10-30  9:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 14:46 [PATCH v2 0/4] Add support for the Renesas RZ/N1 ADC Herve Codina (Schneider Electric)
2025-10-29 14:46 ` [PATCH v2 1/4] dt-bindings: iio: adc: Add " Herve Codina (Schneider Electric)
2025-10-30 18:02   ` Rob Herring (Arm)
2025-10-29 14:46 ` [PATCH v2 2/4] iio: adc: Add support for " Herve Codina (Schneider Electric)
2025-10-30  9:00   ` Andy Shevchenko [this message]
2025-11-02 11:42     ` Jonathan Cameron
2025-11-03  8:40     ` Herve Codina
2025-11-03  9:39       ` Andy Shevchenko
2025-11-03 11:34   ` Nuno Sá
2025-10-29 14:46 ` [PATCH v2 3/4] ARM: dts: renesas: r9a06g032: Add the ADC device Herve Codina (Schneider Electric)
2025-10-29 14:46 ` [PATCH v2 4/4] MAINTAINERS: Add the Renesas RZ/N1 ADC driver entry Herve Codina (Schneider Electric)

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=aQMpHDwCqcrNrnT9@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=geert+renesas@glider.be \
    --cc=herve.codina@bootlin.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=nuno.sa@analog.com \
    --cc=pascal.eberhard@se.com \
    --cc=robh@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wsa+renesas@sang-engineering.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