Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chi-Wen Weng <cwweng.linux@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	cwweng@nuvoton.com
Subject: Re: [PATCH v3 2/2] iio: adc: Add Nuvoton MA35D1 EADC driver
Date: Mon, 2 Nov 2026 12:22:28 +0800	[thread overview]
Message-ID: <81173139-a43c-48a4-97c7-0a82de158b3e@gmail.com> (raw)
In-Reply-To: <20261101005312.1ec5e393@jic23-hlaptop>



Jonathan Cameron 於 2026/11/1 上午 08:53 寫道:
> On Fri, 30 Oct 2026 11:15:01 +0800
> Chi-Wen Weng <cwweng.linux@gmail.com> wrote:
> 
>> From: Chi-Wen Weng <cwweng@nuvoton.com>
>>
>> Add an IIO driver for the Enhanced Analog-to-Digital Converter (EADC)
>> found on Nuvoton MA35D1 SoCs.
>>
>> The driver supports direct conversion and externally triggered buffered
>> capture using sample module 0. Both single-ended inputs and the four
>> fixed differential input pairs are supported.
>>
>> Use the internal 1.6 V reference when no external reference supply is
>> provided, and report the reference voltage through the IIO scale
>> interface.
>>
>> Use ADINT0 for conversion completion. Configure the interrupt source
>> and end-of-conversion position explicitly, and recover from conversion
>> timeouts by resetting the EADC control circuits, synchronizing the IRQ
>> and clearing stale conversion state before another conversion is
>> started.
>>
>> Reset the EADC control circuits during hardware initialization and
>> sanitize interrupt, compare and sample-module trigger configuration so
>> the driver does not depend on state left by firmware when the external
>> reset control is unavailable.
>>
>> Provide firmware-node channel translation so DT IIO consumers select
>> channels by the logical channel index described by the channel node's
>> reg property rather than by the position of the channel in the driver's
>> channel array.
>>
>> Add clock, optional reset and system sleep handling, and restore the
>> controller configuration after resume.
>>
>> Signed-off-by: Chi-Wen Weng <cwweng@nuvoton.com>
> Hi Chi-Wen
> 
> Various comments inline.
> 
> Thanks,
> 
> Jonathan
> 
>> diff --git a/drivers/iio/adc/ma35d1_eadc.c b/drivers/iio/adc/ma35d1_eadc.c
>> new file mode 100644
>> index 000000000000..9b6c38a66a66
>> --- /dev/null
>> +++ b/drivers/iio/adc/ma35d1_eadc.c
> 
> 
>> +
>> +static int ma35d1_adc_disable_irq(struct ma35d1_adc *adc)
>> +{
>> +	return regmap_clear_bits(adc->regmap, MA35D1_EADC_CTL, MA35D1_EADC_CTL_ADCIEN0);
>> +}
>> +
>> +static int ma35d1_adc_setup_reference(struct ma35d1_adc *adc)
>> +{
>> +	struct regmap *map = adc->regmap;
>> +	int ret;
>> +
>> +	/*
>> +	 * MA35D1 TRM EADC reference control: PDREF selects the external VREF
>> +	 * pin. With the internal reference selected, VREFSEL = 0 selects 1.6 V.
>> +	 */
>> +	if (adc->vref) {
> 
> With change below to use the read_voltage function this would then be
> using a flag set there.
> 
>> +		ret = regmap_set_bits(map, MA35D1_EADC_REFADJCTL,
>> +				      MA35D1_EADC_REFADJCTL_PDREF);
>> +		if (ret)
>> +			return ret;
>> +	} else {
>> +		ret = regmap_clear_bits(map, MA35D1_EADC_REFADJCTL,
>> +					MA35D1_EADC_REFADJCTL_PDREF);
>> +		if (ret)
>> +			return ret;
>> +
>> +		ret = regmap_update_bits(map, MA35D1_EADC_CTL,
>> +					 MA35D1_EADC_CTL_VREFSEL_MASK,
>> +					 MA35D1_EADC_CTL_VREFSEL_1V6);
>> +		if (ret)
>> +			return ret;
>> +	}
>> +
>> +	fsleep(MA35D1_EADC_REF_STABLE_US);
>> +
>> +	return 0;
>> +}
> 
> 
>> +static int ma35d1_adc_abort_conversion(struct ma35d1_adc *adc)
>> +{
>> +	struct regmap *map = adc->regmap;
>> +	int ret;
>> +	int err;
>> +
>> +	ret = ma35d1_adc_disable_irq(adc);
>> +
>> +	/*
>> +	 * Reset the EADC control circuits to terminate a conversion which may
>> +	 * still be in progress. EADCRST is cleared automatically by hardware
>> +	 * when the reset completes and the EADC register values are preserved.
>> +	 */
>> +	err = ma35d1_adc_reset_control(adc);
>> +	if (!ret)
>> +		ret = err;
> Why not just set ret directly for this one?
>> +
>> +	/* Drain an interrupt which may already have been latched by the GIC. */
>> +	synchronize_irq(adc->irq);
>> +
>> +	err = regmap_write(map, MA35D1_EADC_STATUS2,
>> +			   MA35D1_EADC_STATUS2_ADIF0);
> I don't mind going slightly over 80 chars. I would do so for the line above.
> 
>> +	if (!ret)
>> +		ret = err;
>> +
>> +	reinit_completion(&adc->completion);
> Why?  It is reinit at start of read conversion - why else do we need to
> do it?  Add a comment
> 
>> +
>> +	return ret;
>> +}
>> +
>> +static int ma35d1_adc_read_conversion(struct ma35d1_adc *adc,
>> +				      const struct iio_chan_spec *chan, u16 *raw)
>> +{
>> +	struct regmap *map = adc->regmap;
>> +	unsigned int val;
>> +	long timeout;
>> +	int ret;
>> +
>> +	reinit_completion(&adc->completion);
>> +
>> +	ret = regmap_write(map, MA35D1_EADC_STATUS2, MA35D1_EADC_STATUS2_ADIF0);
>> +	if (ret)
>> +		return ret;
>> +
>> +	ret = ma35d1_adc_config_channel(adc, chan);
>> +	if (ret)
>> +		return ret;
>> +
>> +	ret = regmap_set_bits(map, MA35D1_EADC_CTL, MA35D1_EADC_CTL_ADCIEN0);
>> +	if (ret)
>> +		return ret;
>> +
>> +	ret = regmap_write(map, MA35D1_EADC_SWTRG, BIT(0));
>> +	if (ret)
>> +		goto disable_irq;
>> +
>> +	timeout = wait_for_completion_timeout(&adc->completion,
>> +					      MA35D1_EADC_TIMEOUT);
>> +	if (!timeout) {
>> +		ret = ma35d1_adc_abort_conversion(adc);
>> +		return ret ?: -ETIMEDOUT;
> 
> Timed out first, so I think that should be the return value
> even if the abort then failed.  Maybe an error print is
> more appropriate for a failed abort so we don't loose
> that extra info.
> 
>> +	}
>> +
>> +	ret = ma35d1_adc_disable_irq(adc);
>> +	if (ret)
>> +		return ret;
>> +
>> +	ret = regmap_read(map, MA35D1_EADC_DAT(0), &val);
>> +	if (ret)
>> +		return ret;
>> +
>> +	if (!(val & MA35D1_EADC_DAT_VALID))
>> +		return -EIO;
>> +
>> +	if (val & MA35D1_EADC_DAT_OV)
>> +		return -EOVERFLOW;
>> +
>> +	*raw = FIELD_GET(MA35D1_EADC_DAT_RESULT_MASK, val);
> 
> As below - I don't follow why we'd get 16 bits when I think
> all paths throw away everything above the 12th.
> 
>> +
>> +	return 0;
>> +
>> +disable_irq:
>> +	ma35d1_adc_disable_irq(adc);
>> +
>> +	return ret;
>> +}
>> +
>> +static irqreturn_t ma35d1_adc_isr(int irq, void *data)
>> +{
>> +	struct iio_dev *indio_dev = data;
>> +	struct ma35d1_adc *adc = iio_priv(indio_dev);
>> +	unsigned int status;
>> +	int ret;
>> +
>> +	ret = regmap_read(adc->regmap, MA35D1_EADC_STATUS2, &status);
>> +	if (ret || !(status & MA35D1_EADC_STATUS2_ADIF0))
>> +		return IRQ_NONE;
>> +
>> +	regmap_write(adc->regmap, MA35D1_EADC_STATUS2,
>> +		     MA35D1_EADC_STATUS2_ADIF0);
>> +	complete(&adc->completion);
>> +
>> +	return IRQ_HANDLED;
>> +}
>> +
>> +static int ma35d1_adc_sign_extend(u16 raw)
>> +{
>> +	return sign_extend32(raw & MA35D1_EADC_DAT_RESULT_12BIT, 11);
> 
> If the result is always 12 bits, why is read_conversion returning 16?
> 
>> +}
>> +
>> +static int ma35d1_adc_read_raw(struct iio_dev *indio_dev,
>> +			       const struct iio_chan_spec *chan,
>> +			       int *val, int *val2, long mask)
>> +{
>> +	struct ma35d1_adc *adc = iio_priv(indio_dev);
>> +	u16 raw;
>> +	int ret;
>> +
>> +	switch (mask) {
>> +	case IIO_CHAN_INFO_RAW: {
>> +		IIO_DEV_ACQUIRE_DIRECT_MODE(indio_dev, claim);
>> +
> 
> No blank line here.  We want the acquire and the error check tightly
> coupled visually.
> 
>> +		if (IIO_DEV_ACQUIRE_FAILED(claim))
>> +			return -EBUSY;
>> +
>> +		guard(mutex)(&adc->lock);
>> +		if (adc->suspended)
>> +			return -EBUSY;
>> +
>> +		ret = ma35d1_adc_read_conversion(adc, chan, &raw);
>> +		if (ret)
>> +			return ret;
>> +
>> +		if (chan->differential)
>> +			*val = ma35d1_adc_sign_extend(raw);
>> +		else
>> +			*val = raw & MA35D1_EADC_DAT_RESULT_12BIT;
>> +
>> +		return IIO_VAL_INT;
>> +	}
>> +	case IIO_CHAN_INFO_SCALE:
>> +		*val = adc->vref_mV;
>> +		/* Differential mode has a VREF / 2048 LSB; single-ended uses /4096. */
>> +		*val2 = chan->differential ? 11 : 12;
>> +		return IIO_VAL_FRACTIONAL_LOG2;
>> +	default:
>> +		return -EINVAL;
>> +	}
>> +}
>> +
>> +static int ma35d1_adc_update_scan_mode(struct iio_dev *indio_dev,
>> +				       const unsigned long *scan_mask)
>> +{
>> +	struct ma35d1_adc *adc = iio_priv(indio_dev);
>> +	const struct iio_chan_spec *scan_chan = NULL;
>> +	unsigned long bit;
>> +
>> +	for_each_set_bit(bit, scan_mask, iio_get_masklength(indio_dev)) {
> 	iio_for_each_active_channel()
> 
>> +		const struct iio_chan_spec *chan = &indio_dev->channels[bit];
>> +
>> +		if (chan->type == IIO_TIMESTAMP)
>> +			continue;
>> +
>> +		if (chan->type != IIO_VOLTAGE || scan_chan)
>> +			return -EINVAL;
>> +
>> +		scan_chan = chan;
> 
> This only makes sense if there is only one channel enabled.
> The driver needs to ensure that is the case (there is a standard
> validation callback for this).
> 
>> +	}
>> +
>> +	if (!scan_chan)
>> +		return -EINVAL;
>> +
>> +	adc->scan_chan = scan_chan;
>> +
>> +	return 0;
>> +}
> 
>> +
>> +static irqreturn_t ma35d1_adc_trigger_handler(int irq, void *p)
> This looks like the device only supports onehot channels (one at a time)
> That's fine but then you should have the callbacks or available_channels
> set to indicate that.
> 
>> +{
>> +	struct iio_poll_func *pf = p;
>> +	struct iio_dev *indio_dev = pf->indio_dev;
>> +	struct ma35d1_adc *adc = iio_priv(indio_dev);
>> +	IIO_DECLARE_BUFFER_WITH_TS(u16, scan, 1) = { };
> Where the timestamp location is fixed (if present) I prefer
> 	struct {
> 		u16 channel;
> 		aligned_s64 timestamp;
> 	} scan;
> 
> as it makes it easier to understand the layout. The macro
> is for the case where different numbers of channels can be enabled
> and there are enough of them to have the timestamp moving around
> depending on what is enabled.
> 
>> +	u16 raw;
>> +	int ret;
>> +
>> +	mutex_lock(&adc->lock);
>> +
>> +	if (!adc->suspended && adc->scan_chan) {
>> +		ret = ma35d1_adc_read_conversion(adc, adc->scan_chan, &raw);
>> +		if (!ret) {
>> +			scan[0] = raw & MA35D1_EADC_DAT_RESULT_12BIT;
>> +			iio_push_to_buffers_with_ts(indio_dev, scan, sizeof(scan),
>> +						    pf->timestamp);
>> +		}
>> +	}
>> +
>> +	mutex_unlock(&adc->lock);
>> +
>> +	iio_trigger_notify_done(indio_dev->trig);
>> +
>> +	return IRQ_HANDLED;
>> +}
> 
>> +
>> +static int ma35d1_adc_fwnode_xlate(struct iio_dev *indio_dev,
>> +				   const struct fwnode_reference_args *iiospec)
>> +{
>> +	unsigned int i;
>> +
>> +	if (iiospec->nargs != 1)
>> +		return -EINVAL;
>> +
>> +	for (i = 0; i < indio_dev->num_channels; i++) {
> 
> 	for (unsigned int i = 0; ..
> 
>> +		const struct iio_chan_spec *chan = &indio_dev->channels[i];
>> +
>> +		if (chan->type == IIO_VOLTAGE &&
>> +		    chan->channel == iiospec->args[0])
>> +			return i;
>> +	}
>> +
>> +	return -EINVAL;
>> +}
>> +
>> +static const struct iio_info ma35d1_adc_info = {
>> +	.read_raw = ma35d1_adc_read_raw,
>> +	.update_scan_mode = ma35d1_adc_update_scan_mode,
>> +	.fwnode_xlate = ma35d1_adc_fwnode_xlate,
>> +};
>> +
>> +static void ma35d1_adc_init_channel(struct iio_chan_spec *chan, u32 index,
> 
> As below.  Given C provides nice ways to set lots of structure elements
> helpers use those, rather than a fill the values in helper.
> 
>> +				    u32 vinp, u32 vinn,
>> +				    unsigned int scan_index,
>> +				    bool differential)
>> +{
>> +	chan->type = IIO_VOLTAGE;
>> +	chan->indexed = 1;
>> +	chan->channel = index;
>> +	chan->address = vinp;
>> +	chan->scan_index = scan_index;
>> +	chan->info_mask_separate =
>> +		BIT(IIO_CHAN_INFO_RAW) | BIT(IIO_CHAN_INFO_SCALE);
>> +	chan->scan_type.format = differential ? IIO_SCAN_FORMAT_SIGNED_INT :
>> +					      IIO_SCAN_FORMAT_UNSIGNED_INT;
>> +	chan->scan_type.realbits = 12;
>> +	chan->scan_type.storagebits = 16;
>> +	chan->scan_type.endianness = IIO_CPU;
>> +
>> +	if (differential) {
>> +		chan->differential = 1;
>> +		chan->channel2 = vinn;
>> +	}
>> +}
>> +
>> +static int ma35d1_adc_parse_channels(struct iio_dev *indio_dev,
>> +				     struct device *dev)
>> +{
>> +	DECLARE_BITMAP(used_regs, MA35D1_EADC_MAX_EXT_CHANNELS);
>> +	struct iio_chan_spec *channels;
>> +	unsigned int scan_index;
>> +	int num_channels;
>> +	int ret;
>> +
>> +	bitmap_zero(used_regs, MA35D1_EADC_MAX_EXT_CHANNELS);
>> +
>> +	num_channels = device_get_child_node_count(dev);
>> +	if (!num_channels)
>> +		return dev_err_probe(dev, -ENOENT, "no ADC channels configured\n");
>> +
>> +	if (num_channels > MA35D1_EADC_MAX_EXT_CHANNELS)
>> +		return dev_err_probe(dev, -EINVAL, "too many ADC channels\n");
>> +
>> +	channels = devm_kcalloc(dev, size_add(num_channels, 1),
>> +				sizeof(*channels), GFP_KERNEL);
>> +	if (!channels)
>> +		return -ENOMEM;
>> +
>> +	scan_index = 0;
>> +	device_for_each_child_node_scoped(dev, child) {
>> +		bool differential;
>> +		u32 reg;
>> +		u32 vinp;
>> +		u32 vinn;
> 
> Can combine these related u32s on oneline.
> 
>> +
>> +		ret = fwnode_property_read_u32(child, "reg", &reg);
>> +		if (ret)
>> +			return dev_err_probe(dev, ret,
>> +					     "missing channel reg property\n");
>> +
>> +		if (reg >= MA35D1_EADC_MAX_EXT_CHANNELS)
>> +			return dev_err_probe(dev, -EINVAL,
>> +					     "invalid ADC channel index %u\n", reg);
>> +
>> +		if (test_and_set_bit(reg, used_regs))
>> +			return dev_err_probe(dev, -EINVAL,
>> +					     "duplicate ADC channel index %u\n", reg);
>> +
>> +		if (fwnode_property_present(child, "single-channel")) {
>> +			ret = fwnode_property_read_u32(child, "single-channel",
>> +						       &vinp);
>> +			if (ret)
>> +				return dev_err_probe(dev, ret,
>> +						     "invalid single-channel for index %u\n",
>> +						     reg);
>> +
>> +			if (vinp >= MA35D1_EADC_MAX_EXT_CHANNELS)
>> +				return dev_err_probe(dev, -EINVAL,
>> +						     "invalid ADC input %u\n", vinp);
>> +
>> +			vinn = 0;
>> +			differential = false;
>> +		} else {
> 
> This will change to match my requests for the binding so I won't look too closely
> at it in this revision.
> 
>> +			if (reg >= 4)
>> +				return dev_err_probe(dev, -EINVAL,
>> +						     "invalid differential pair %u\n", reg);
>> +
>> +			vinp = reg;
>> +			vinn = reg + 4;
>> +			differential = true;
>> +		}
>> +
>> +		ma35d1_adc_init_channel(&channels[scan_index], reg, vinp, vinn,
>> +					scan_index, differential);
> get rid of this and fill the structure in directly in the two different
> paths above - so have a single ended copy of this and the slightly
> different one for the differential channels. Bit of duplication
> but simpler code by putting it all in one place.
> 
> 			channels[scan_index] = (struct iio_chan_spec) {
> 				.type = IIO_VOLTAGE,
> 				.indexed = 1,
> 				.channel = index,
> 				.address = vinp,
> 				.scan_index = scan_index,
> 				.info_mask_separate = BIT(IIO_CHAN_INFO_RAW) |
> 						      BIT(IIO_CHAN_INFO_SCALE);
> 				.scan_type = {
> 					.format = IIO_SCAN_FORMAT_UNSIGNED_INT,
> 					.realbits = 12,
> 					.storagebits = 16,
> 					.endianness = IIO_CPU,;
> 			};
> 		
>> +		scan_index++;
> 
>> +	}
>> +
>> +	channels[scan_index] = IIO_CHAN_SOFT_TIMESTAMP(scan_index);
> 
>> +
>> +	indio_dev->channels = channels;
>> +	indio_dev->num_channels = scan_index + 1;
>> +
>> +	return 0;
>> +}
>> +
>> +static int ma35d1_adc_init_vref(struct ma35d1_adc *adc, struct device *dev)
>> +{
>> +	int ret;
>> +
>> +	adc->vref = devm_regulator_get_optional(dev, "vref");
>> +	ret = PTR_ERR_OR_ZERO(adc->vref);
>> +	if (ret == -ENODEV) {
>> +		adc->vref = NULL;
>> +		adc->vref_mV = MA35D1_EADC_INTERNAL_VREF_mV;
>> +		return 0;
>> +	}
>> +	if (ret)
>> +		return dev_err_probe(dev, ret, "failed to get VREF supply\n");
>> +
>> +	ret = regulator_enable(adc->vref);
>> +	if (ret)
>> +		return dev_err_probe(dev, ret, "failed to enable VREF supply\n");
>> +
>> +	ret = devm_add_action_or_reset(dev, ma35d1_adc_vref_disable, adc->vref);
>> +	if (ret)
>> +		return ret;
>> +
>> +	ret = regulator_get_voltage(adc->vref);
> 
> There are plenty of examples of how to use devm_regulator_get_enable_read_voltage()
> with optional regulators in tree.  Follow one of those and this code will be a lot
> shorter.
> 
>> +	if (ret <= 0)
>> +		return dev_err_probe(dev, ret ?: -EINVAL,
>> +				     "failed to get VREF voltage\n");
>> +
>> +	adc->vref_mV = ret / (MICRO / MILLI);
>> +
>> +	return 0;
>> +}
> 
>> +static int ma35d1_adc_suspend(struct device *dev)
>> +{
>> +	struct iio_dev *indio_dev = dev_get_drvdata(dev);
>> +	struct ma35d1_adc *adc = iio_priv(indio_dev);
>> +	int ret;
>> +
>> +	ret = iio_device_suspend_triggering(indio_dev);
>> +	if (ret)
>> +		return ret;
>> +
>> +	mutex_lock(&adc->lock);
>> +
>> +	ret = ma35d1_adc_disable_irq(adc);
>> +	if (ret)
>> +		goto resume_triggering;
>> +
>> +	synchronize_irq(adc->irq);
>> +
>> +	ret = regmap_clear_bits(adc->regmap, MA35D1_EADC_CTL,
>> +				MA35D1_EADC_CTL_ADCEN);
>> +	if (ret)
> 
> If this fails, for consistency I think you should probably
> reenable the irq.  If not add a comment on your thinking for
> why.
> 
>   
>> +		goto resume_triggering;
>> +
>> +	adc->suspended = true;
>> +	clk_disable_unprepare(adc->clk);
>> +	mutex_unlock(&adc->lock);
>> +
>> +	return 0;
>> +
>> +resume_triggering:
>> +	mutex_unlock(&adc->lock);
>> +	iio_device_resume_triggering(indio_dev);
>> +
>> +	return ret;
>> +}
>> +
> 

Hi Jonathan,

Thank you for the detailed review.

I will address these comments in v4.

The channel parsing will be reworked together with the binding changes.
reg will remain the logical channel index, while single-channel and
diff-channels will describe the physical inputs. Accordingly, the IIO
channel specification will use channel/channel2 for the physical input
or differential pair, while address will keep the logical DT channel
index used for firmware-node translation.

I will also remove ma35d1_adc_init_channel() and initialize the
iio_chan_spec structures directly in the single-ended and differential
parsing paths.

Regarding the one-hot scan-mask handling, the MA35D1 hardware itself is
not limited to one sample module at a time. The EADC has one SAR
converter shared by multiple sample modules. Multiple sample modules can
be triggered together, after which the hardware priority arbitrator
performs their conversions sequentially.

The initial driver, however, currently uses only sample module 0 and
performs one voltage conversion for each buffered trigger. Therefore
the buffered interface exposed by this version of the driver supports
one active voltage channel per scan. I will make this limitation
explicit using the standard one-hot scan-mask validation callback and
use iio_for_each_active_channel() when selecting the active channel.
Support for using multiple sample modules for multi-channel buffered
scans can be added separately in the future.

Since the scan layout is therefore fixed to one u16 sample plus an
optional timestamp, I will replace IIO_DECLARE_BUFFER_WITH_TS() with a
fixed scan structure containing one u16 sample and an aligned timestamp.

For the conversion path I will make the returned ADC sample explicitly
12 bits. Differential values will then be sign-extended directly from
that 12-bit value, rather than carrying a 16-bit intermediate result
whose upper bits are discarded later.

For timeout recovery I will keep -ETIMEDOUT as the primary error. If
resetting or aborting the timed-out conversion fails, I will report that
separately instead of replacing the timeout return value. I will also
remove the redundant completion reinitialization from the abort path,
since the completion is reinitialized before each new conversion and
the abort path already synchronizes the IRQ.

I will simplify the optional VREF handling using
devm_regulator_get_enable_read_voltage() and keep a flag indicating
whether the external reference is in use.

Regarding the suspend error path, ADCIEN0 is only enabled while a
conversion is in progress and is normally disabled while the device is
idle. The suspend path holds the device lock after triggering has been
suspended, so there is no active conversion at that point. If disabling
ADCEN fails, leaving ADCIEN0 disabled therefore matches the normal idle
state, and the next conversion will enable it again. I will add a
comment to make this state transition clear rather than unconditionally
re-enabling the interrupt.

I will also take care of the smaller style points, including keeping the
direct-mode acquire and error check together, using a loop-local
variable in fwnode_xlate(), combining the related u32 declarations, and
avoiding unnecessary line wrapping.

Thanks,
Chi-Wen



      reply	other threads:[~2026-11-02  4:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30  3:14 [PATCH v3 0/2] iio: adc: Add Nuvoton MA35D1 EADC support Chi-Wen Weng
2026-10-30  3:15 ` [PATCH v3 1/2] dt-bindings: iio: adc: Add Nuvoton MA35D1 EADC Chi-Wen Weng
2026-11-01  0:19   ` Jonathan Cameron
2026-11-02  2:38     ` Chi-Wen Weng
2026-11-02 10:03   ` Krzysztof Kozlowski
2026-11-02 10:20     ` Chi-Wen Weng
2026-10-30  3:15 ` [PATCH v3 2/2] iio: adc: Add Nuvoton MA35D1 EADC driver Chi-Wen Weng
2026-11-01  0:53   ` Jonathan Cameron
2026-11-02  4:22     ` Chi-Wen Weng [this message]

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=81173139-a43c-48a4-97c7-0a82de158b3e@gmail.com \
    --to=cwweng.linux@gmail.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cwweng@nuvoton.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.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