* [PATCH v3 1/3] iio: adc: ti-ads112c14: add DRDY interrupt support
2026-08-07 21:19 [PATCH v3 0/3] iio: adc: ti-ads112c14: continuous mode support David Lechner (TI)
@ 2026-08-07 21:19 ` David Lechner (TI)
2026-08-10 8:50 ` Andy Shevchenko
2026-08-07 21:19 ` [PATCH v3 2/3] iio: adc: ti-ads112c14: create data read helper functions David Lechner (TI)
2026-08-07 21:19 ` [PATCH v3 3/3] iio: adc: ti-ads112c14: add continuous mode support David Lechner (TI)
2 siblings, 1 reply; 9+ messages in thread
From: David Lechner (TI) @ 2026-08-07 21:19 UTC (permalink / raw)
To: Jonathan Cameron, Nuno Sá, Andy Shevchenko
Cc: Chris Hall, Patrick Edwards, Kurt Borja, linux-iio, linux-kernel,
David Lechner (TI)
Add handling for the DRDY interrupt to wait for data ready events rather
than polling (only when it is wired up).
Signed-off-by: David Lechner (TI) <dlechner@baylibre.com>
---
Small note: the hard-coded 100 ms timeout will be replaced in a future
series with a dynamic value, so I didn't bother with a macro or comments
to explain why the value was chosen.
And passing indio_dev instead of data to irq is intentional as it will
be used in the next patch.
---
drivers/iio/adc/ti-ads112c14.c | 100 ++++++++++++++++++++++++++++++++++++-----
1 file changed, 90 insertions(+), 10 deletions(-)
diff --git a/drivers/iio/adc/ti-ads112c14.c b/drivers/iio/adc/ti-ads112c14.c
index 60eab4852ba2..457d2db28d3f 100644
--- a/drivers/iio/adc/ti-ads112c14.c
+++ b/drivers/iio/adc/ti-ads112c14.c
@@ -10,6 +10,7 @@
#include <linux/bitfield.h>
#include <linux/cleanup.h>
+#include <linux/completion.h>
#include <linux/crc8.h>
#include <linux/delay.h>
#include <linux/dev_printk.h>
@@ -19,6 +20,7 @@
#include <linux/iio/iio.h>
#include <linux/iio/trigger_consumer.h>
#include <linux/iio/triggered_buffer.h>
+#include <linux/interrupt.h>
#include <linux/math64.h>
#include <linux/minmax.h>
#include <linux/module.h>
@@ -117,9 +119,15 @@
#define ADS112C14_GPIO_CFG_GPIO2_CFG GENMASK(5, 4)
#define ADS112C14_GPIO_CFG_GPIO1_CFG GENMASK(3, 2)
#define ADS112C14_GPIO_CFG_GPIO0_CFG GENMASK(1, 0)
+#define ADS112C14_GPIO_CFG_GPIO_CFG_DISABLED 0
+#define ADS112C14_GPIO_CFG_GPIO_CFG_INPUT 1
+#define ADS112C14_GPIO_CFG_GPIO_CFG_OUTPUT_PUSH_PULL 2
+#define ADS112C14_GPIO_CFG_GPIO_CFG_OUTPUT_OPEN_DRAIN 3
#define ADS112C14_REG_GPIO_DATA_OUTPUT 0x0C
#define ADS112C14_GPIO_DATA_OUTPUT_GPIO3_SRC BIT(7)
+#define ADS112C14_GPIO_DATA_OUTPUT_GPIO3_SRC_DAT_OUT 0
+#define ADS112C14_GPIO_DATA_OUTPUT_GPIO3_SRC_DRDY 1
#define ADS112C14_GPIO_DATA_OUTPUT_GPIO2_SRC BIT(6)
#define ADS112C14_GPIO_DATA_OUTPUT_GPIO3_DAT_OUT BIT(3)
#define ADS112C14_GPIO_DATA_OUTPUT_GPIO2_DAT_OUT BIT(2)
@@ -251,6 +259,8 @@ struct ads112c14_data {
struct regmap *regmap;
/* Synchronizes access to register value fields. */
struct mutex lock;
+ int drdy_irq;
+ struct completion drdy_completion;
bool i2c_crc_enabled;
u32 avdd_uV;
u32 ext_ref_uV;
@@ -265,6 +275,16 @@ struct ads112c14_data {
ARRAY_SIZE(ads112c14_sys_mon_channels));
};
+static irqreturn_t ads112c14_drdy_irq_handler(int irq, void *private)
+{
+ struct iio_dev *indio_dev = private;
+ struct ads112c14_data *data = iio_priv(indio_dev);
+
+ complete(&data->drdy_completion);
+
+ return IRQ_HANDLED;
+}
+
static bool ads112c14_writeable_reg(struct device *dev, unsigned int reg)
{
switch (reg) {
@@ -581,12 +601,45 @@ static int ads112c14_prepare_sys_mon_channel(struct ads112c14_data *data,
return 0;
}
+static int ads112c14_wait_for_conversion_irq(struct ads112c14_data *data)
+{
+ unsigned long remaining;
+ int ret;
+
+ reinit_completion(&data->drdy_completion);
+
+ ret = regmap_write(data->regmap, ADS112C14_REG_CONVERSION_CTRL,
+ ADS112C14_CONVERSION_CTRL_START);
+ if (ret)
+ return ret;
+
+ remaining = wait_for_completion_timeout(&data->drdy_completion,
+ msecs_to_jiffies(100));
+
+ return remaining ? 0 : -ETIMEDOUT;
+}
+
+static int ads112c14_wait_for_conversion_poll(struct ads112c14_data *data)
+{
+ u32 reg_val;
+ int ret;
+
+ ret = regmap_write(data->regmap, ADS112C14_REG_CONVERSION_CTRL,
+ ADS112C14_CONVERSION_CTRL_START);
+ if (ret)
+ return ret;
+
+ return regmap_read_poll_timeout(data->regmap,
+ ADS112C14_REG_STATUS_MSB, reg_val,
+ FIELD_GET(ADS112C14_STATUS_MSB_DRDY, reg_val),
+ 1 * USEC_PER_MSEC, 100 * USEC_PER_MSEC);
+}
+
static int ads112c14_single_conversion(struct ads112c14_data *data,
const struct iio_chan_spec *chan,
u8 *buf, bool for_scan)
{
struct i2c_client *client = to_i2c_client(regmap_get_device(data->regmap));
- u32 reg_val;
int ret;
guard(mutex)(&data->lock);
@@ -601,15 +654,10 @@ static int ads112c14_single_conversion(struct ads112c14_data *data,
return ret;
}
- ret = regmap_write(data->regmap, ADS112C14_REG_CONVERSION_CTRL,
- ADS112C14_CONVERSION_CTRL_START);
- if (ret)
- return ret;
-
- ret = regmap_read_poll_timeout(data->regmap,
- ADS112C14_REG_STATUS_MSB, reg_val,
- FIELD_GET(ADS112C14_STATUS_MSB_DRDY, reg_val),
- 1 * USEC_PER_MSEC, 100 * USEC_PER_MSEC);
+ if (data->drdy_irq)
+ ret = ads112c14_wait_for_conversion_irq(data);
+ else
+ ret = ads112c14_wait_for_conversion_poll(data);
if (ret)
return ret;
@@ -1391,6 +1439,38 @@ static int ads112c14_probe(struct i2c_client *client)
if (ret)
return ret;
+ if (device_property_present(dev, "interrupts")) {
+ data->drdy_irq = fwnode_irq_get_byname(dev_fwnode(dev), "drdy");
+ if (data->drdy_irq < 0)
+ return dev_err_probe(dev, data->drdy_irq,
+ "failed to get drdy interrupt\n");
+
+ /*
+ * REVISIT: would probably need to implement a pin controller in
+ * order to support open drain option here.
+ */
+ ret = regmap_update_bits(data->regmap, ADS112C14_REG_GPIO_CFG,
+ ADS112C14_GPIO_CFG_GPIO3_CFG,
+ FIELD_PREP(ADS112C14_GPIO_CFG_GPIO3_CFG,
+ ADS112C14_GPIO_CFG_GPIO_CFG_OUTPUT_PUSH_PULL));
+ if (ret)
+ return ret;
+
+ ret = regmap_update_bits(data->regmap, ADS112C14_REG_GPIO_DATA_OUTPUT,
+ ADS112C14_GPIO_DATA_OUTPUT_GPIO3_SRC,
+ FIELD_PREP(ADS112C14_GPIO_DATA_OUTPUT_GPIO3_SRC,
+ ADS112C14_GPIO_DATA_OUTPUT_GPIO3_SRC_DRDY));
+ if (ret)
+ return ret;
+
+ init_completion(&data->drdy_completion);
+
+ ret = devm_request_irq(dev, data->drdy_irq, ads112c14_drdy_irq_handler,
+ 0, dev_name(dev), indio_dev);
+ if (ret)
+ return ret;
+ }
+
ads112c14_populate_tables(data);
indio_dev->name = info->name;
--
2.43.0
^ permalink raw reply related [flat|nested] 9+ messages in thread* Re: [PATCH v3 1/3] iio: adc: ti-ads112c14: add DRDY interrupt support
2026-08-07 21:19 ` [PATCH v3 1/3] iio: adc: ti-ads112c14: add DRDY interrupt support David Lechner (TI)
@ 2026-08-10 8:50 ` Andy Shevchenko
2026-08-10 15:59 ` David Lechner
0 siblings, 1 reply; 9+ messages in thread
From: Andy Shevchenko @ 2026-08-10 8:50 UTC (permalink / raw)
To: David Lechner (TI)
Cc: Jonathan Cameron, Nuno Sá, Andy Shevchenko, Chris Hall,
Patrick Edwards, Kurt Borja, linux-iio, linux-kernel
On Fri, Aug 07, 2026 at 04:19:46PM -0500, David Lechner (TI) wrote:
> Add handling for the DRDY interrupt to wait for data ready events rather
> than polling (only when it is wired up).
...
> +static irqreturn_t ads112c14_drdy_irq_handler(int irq, void *private)
> +{
> + struct iio_dev *indio_dev = private;
> + struct ads112c14_data *data = iio_priv(indio_dev);
I have seen some discussion about this, but what's the problem with the
struct ads112c14_data *data = iio_priv(private);
?
> + complete(&data->drdy_completion);
> +
> + return IRQ_HANDLED;
> +}
...
> + if (device_property_present(dev, "interrupts")) {
Unfortunately this is no-go for ACPI-enabled systems.
On ACPI we expect to have 'interrupt-names' but 'interrupts' is OF-only.
> + data->drdy_irq = fwnode_irq_get_byname(dev_fwnode(dev), "drdy");
> + if (data->drdy_irq < 0)
> + return dev_err_probe(dev, data->drdy_irq,
> + "failed to get drdy interrupt\n");
> +
> + /*
> + * REVISIT: would probably need to implement a pin controller in
> + * order to support open drain option here.
> + */
> + ret = regmap_update_bits(data->regmap, ADS112C14_REG_GPIO_CFG,
> + ADS112C14_GPIO_CFG_GPIO3_CFG,
> + FIELD_PREP(ADS112C14_GPIO_CFG_GPIO3_CFG,
> + ADS112C14_GPIO_CFG_GPIO_CFG_OUTPUT_PUSH_PULL));
> + if (ret)
> + return ret;
> +
> + ret = regmap_update_bits(data->regmap, ADS112C14_REG_GPIO_DATA_OUTPUT,
> + ADS112C14_GPIO_DATA_OUTPUT_GPIO3_SRC,
> + FIELD_PREP(ADS112C14_GPIO_DATA_OUTPUT_GPIO3_SRC,
> + ADS112C14_GPIO_DATA_OUTPUT_GPIO3_SRC_DRDY));
> + if (ret)
> + return ret;
> +
> + init_completion(&data->drdy_completion);
> +
> + ret = devm_request_irq(dev, data->drdy_irq, ads112c14_drdy_irq_handler,
> + 0, dev_name(dev), indio_dev);
> + if (ret)
> + return ret;
> + }
--
With Best Regards,
Andy Shevchenko
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [PATCH v3 1/3] iio: adc: ti-ads112c14: add DRDY interrupt support
2026-08-10 8:50 ` Andy Shevchenko
@ 2026-08-10 15:59 ` David Lechner
2026-08-10 17:01 ` Andy Shevchenko
0 siblings, 1 reply; 9+ messages in thread
From: David Lechner @ 2026-08-10 15:59 UTC (permalink / raw)
To: Andy Shevchenko
Cc: Jonathan Cameron, Nuno Sá, Andy Shevchenko, Chris Hall,
Patrick Edwards, Kurt Borja, linux-iio, linux-kernel
On 8/10/26 3:50 AM, Andy Shevchenko wrote:
> On Fri, Aug 07, 2026 at 04:19:46PM -0500, David Lechner (TI) wrote:
>> Add handling for the DRDY interrupt to wait for data ready events rather
>> than polling (only when it is wired up).
>
> ...
>
>> +static irqreturn_t ads112c14_drdy_irq_handler(int irq, void *private)
>> +{
>> + struct iio_dev *indio_dev = private;
>> + struct ads112c14_data *data = iio_priv(indio_dev);
>
> I have seen some discussion about this, but what's the problem with the
>
> struct ads112c14_data *data = iio_priv(private);
>
> ?
indio_dev gets used in a later patch, so point is to avoid churn.
>
>> + complete(&data->drdy_completion);
>> +
>> + return IRQ_HANDLED;
>> +}
>
> ...
>
>> + if (device_property_present(dev, "interrupts")) {
>
> Unfortunately this is no-go for ACPI-enabled systems.
> On ACPI we expect to have 'interrupt-names' but 'interrupts' is OF-only.
So device_property_present(dev, "interrupt-names") is OK?
>
>> + data->drdy_irq = fwnode_irq_get_byname(dev_fwnode(dev), "drdy");
>> + if (data->drdy_irq < 0)
>> + return dev_err_probe(dev, data->drdy_irq,
>> + "failed to get drdy interrupt\n");
>> +
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [PATCH v3 1/3] iio: adc: ti-ads112c14: add DRDY interrupt support
2026-08-10 15:59 ` David Lechner
@ 2026-08-10 17:01 ` Andy Shevchenko
0 siblings, 0 replies; 9+ messages in thread
From: Andy Shevchenko @ 2026-08-10 17:01 UTC (permalink / raw)
To: David Lechner
Cc: Jonathan Cameron, Nuno Sá, Andy Shevchenko, Chris Hall,
Patrick Edwards, Kurt Borja, linux-iio, linux-kernel
On Mon, Aug 10, 2026 at 10:59:20AM -0500, David Lechner wrote:
> On 8/10/26 3:50 AM, Andy Shevchenko wrote:
> > On Fri, Aug 07, 2026 at 04:19:46PM -0500, David Lechner (TI) wrote:
...
> >> + if (device_property_present(dev, "interrupts")) {
> >
> > Unfortunately this is no-go for ACPI-enabled systems.
> > On ACPI we expect to have 'interrupt-names' but 'interrupts' is OF-only.
>
> So device_property_present(dev, "interrupt-names") is OK?
As long as we use _irq_get_byname(), yes. Because the below call relies on that
property to be present in any supported FW description.
> >> + data->drdy_irq = fwnode_irq_get_byname(dev_fwnode(dev), "drdy");
OTOH, you may also introduce _optional() variant for this to avoid layering
violation (why should driver know about that property at all?). But I haven't
checked how many existing users (if any) we have. If none, perhaps also a
TODO/FIXME/et cetera here to point out on this.
--
With Best Regards,
Andy Shevchenko
^ permalink raw reply [flat|nested] 9+ messages in thread
* [PATCH v3 2/3] iio: adc: ti-ads112c14: create data read helper functions
2026-08-07 21:19 [PATCH v3 0/3] iio: adc: ti-ads112c14: continuous mode support David Lechner (TI)
2026-08-07 21:19 ` [PATCH v3 1/3] iio: adc: ti-ads112c14: add DRDY interrupt support David Lechner (TI)
@ 2026-08-07 21:19 ` David Lechner (TI)
2026-08-07 21:19 ` [PATCH v3 3/3] iio: adc: ti-ads112c14: add continuous mode support David Lechner (TI)
2 siblings, 0 replies; 9+ messages in thread
From: David Lechner (TI) @ 2026-08-07 21:19 UTC (permalink / raw)
To: Jonathan Cameron, Nuno Sá, Andy Shevchenko
Cc: Chris Hall, Patrick Edwards, Kurt Borja, linux-iio, linux-kernel,
David Lechner (TI)
Refactor a few bits of code into helper functions. These will be reused
when continuous mode support is added in a later patch.
Signed-off-by: David Lechner (TI) <dlechner@baylibre.com>
---
drivers/iio/adc/ti-ads112c14.c | 51 +++++++++++++++++++++++++-----------------
1 file changed, 31 insertions(+), 20 deletions(-)
diff --git a/drivers/iio/adc/ti-ads112c14.c b/drivers/iio/adc/ti-ads112c14.c
index 457d2db28d3f..8481012c9e3d 100644
--- a/drivers/iio/adc/ti-ads112c14.c
+++ b/drivers/iio/adc/ti-ads112c14.c
@@ -601,6 +601,32 @@ static int ads112c14_prepare_sys_mon_channel(struct ads112c14_data *data,
return 0;
}
+static int ads112c14_prepare_channel(struct ads112c14_data *data,
+ const struct iio_chan_spec *chan)
+{
+ if (chan->channel < ADS112C14_SYS_MON_CHANNEL_BASE)
+ return ads112c14_prepare_measurement_channel(data, chan);
+
+ return ads112c14_prepare_sys_mon_channel(data, chan);
+}
+
+static int ads112c14_scan_read(struct ads112c14_data *data, u8 *buf)
+{
+ struct i2c_client *client = to_i2c_client(regmap_get_device(data->regmap));
+ int ret;
+ u8 len;
+
+ len = BITS_TO_BYTES(data->chip_info->resolution_bits);
+ if (data->i2c_crc_enabled)
+ len += 1;
+
+ ret = i2c_smbus_read_i2c_block_data(client, ADS112C14_CMD_RDATA, len, buf);
+ if (ret < 0)
+ return ret;
+
+ return 0;
+}
+
static int ads112c14_wait_for_conversion_irq(struct ads112c14_data *data)
{
unsigned long remaining;
@@ -644,15 +670,9 @@ static int ads112c14_single_conversion(struct ads112c14_data *data,
guard(mutex)(&data->lock);
- if (chan->channel < ADS112C14_SYS_MON_CHANNEL_BASE) {
- ret = ads112c14_prepare_measurement_channel(data, chan);
- if (ret)
- return ret;
- } else {
- ret = ads112c14_prepare_sys_mon_channel(data, chan);
- if (ret)
- return ret;
- }
+ ret = ads112c14_prepare_channel(data, chan);
+ if (ret)
+ return ret;
if (data->drdy_irq)
ret = ads112c14_wait_for_conversion_irq(data);
@@ -667,17 +687,8 @@ static int ads112c14_single_conversion(struct ads112c14_data *data,
* with CRC errors, but rather leave it to userspace to decide what to
* do.
*/
- if (for_scan) {
- u8 len = BITS_TO_BYTES(data->chip_info->resolution_bits) +
- (data->i2c_crc_enabled ? 1 : 0);
-
- ret = i2c_smbus_read_i2c_block_data(client, ADS112C14_CMD_RDATA,
- len, buf);
- if (ret < 0)
- return ret;
-
- return 0;
- }
+ if (for_scan)
+ return ads112c14_scan_read(data, buf);
return ads112c14_i2c_read_bytes(client, ADS112C14_CMD_RDATA, buf,
BITS_TO_BYTES(data->chip_info->resolution_bits),
--
2.43.0
^ permalink raw reply related [flat|nested] 9+ messages in thread* [PATCH v3 3/3] iio: adc: ti-ads112c14: add continuous mode support
2026-08-07 21:19 [PATCH v3 0/3] iio: adc: ti-ads112c14: continuous mode support David Lechner (TI)
2026-08-07 21:19 ` [PATCH v3 1/3] iio: adc: ti-ads112c14: add DRDY interrupt support David Lechner (TI)
2026-08-07 21:19 ` [PATCH v3 2/3] iio: adc: ti-ads112c14: create data read helper functions David Lechner (TI)
@ 2026-08-07 21:19 ` David Lechner (TI)
2026-08-10 8:58 ` Andy Shevchenko
2026-08-16 20:26 ` Jonathan Cameron
2 siblings, 2 replies; 9+ messages in thread
From: David Lechner (TI) @ 2026-08-07 21:19 UTC (permalink / raw)
To: Jonathan Cameron, Nuno Sá, Andy Shevchenko
Cc: Chris Hall, Patrick Edwards, Kurt Borja, linux-iio, linux-kernel,
David Lechner (TI)
Add support for continuous mode in the TI ADS112C14 ADC driver. In this
mode the ADC itself is starting each conversion, so we add a trigger
based on the DRDY interrupt to read each sample. This mode is also
limited in that only one channel can be enabled at a time since the
chip does not have a sequencer or simultaneous sampling capability.
Continuous mode will only be used when this new trigger is the current
trigger.
Signed-off-by: David Lechner (TI) <dlechner@baylibre.com>
---
drivers/iio/adc/ti-ads112c14.c | 132 ++++++++++++++++++++++++++++++++++++++++-
1 file changed, 130 insertions(+), 2 deletions(-)
diff --git a/drivers/iio/adc/ti-ads112c14.c b/drivers/iio/adc/ti-ads112c14.c
index 8481012c9e3d..160ee306d4a6 100644
--- a/drivers/iio/adc/ti-ads112c14.c
+++ b/drivers/iio/adc/ti-ads112c14.c
@@ -9,6 +9,7 @@
*/
#include <linux/bitfield.h>
+#include <linux/bitmap.h>
#include <linux/cleanup.h>
#include <linux/completion.h>
#include <linux/crc8.h>
@@ -18,6 +19,7 @@
#include <linux/i2c.h>
#include <linux/iio/buffer.h>
#include <linux/iio/iio.h>
+#include <linux/iio/trigger.h>
#include <linux/iio/trigger_consumer.h>
#include <linux/iio/triggered_buffer.h>
#include <linux/interrupt.h>
@@ -257,6 +259,7 @@ struct ads112c14_measurement {
struct ads112c14_data {
const struct ads112c14_chip_info *chip_info;
struct regmap *regmap;
+ struct iio_trigger *drdy_trig;
/* Synchronizes access to register value fields. */
struct mutex lock;
int drdy_irq;
@@ -280,11 +283,18 @@ static irqreturn_t ads112c14_drdy_irq_handler(int irq, void *private)
struct iio_dev *indio_dev = private;
struct ads112c14_data *data = iio_priv(indio_dev);
- complete(&data->drdy_completion);
+ if (indio_dev->trig && iio_trigger_using_own(indio_dev))
+ iio_trigger_poll(data->drdy_trig);
+ else
+ complete(&data->drdy_completion);
return IRQ_HANDLED;
}
+static const struct iio_trigger_ops ads112c14_trigger_ops = {
+ .validate_device = iio_trigger_validate_own_device,
+};
+
static bool ads112c14_writeable_reg(struct device *dev, unsigned int reg)
{
switch (reg) {
@@ -957,10 +967,31 @@ static irqreturn_t ads112c14_trigger_handler(int irq, void *private)
struct iio_poll_func *pf = private;
struct iio_dev *indio_dev = pf->indio_dev;
struct ads112c14_data *data = iio_priv(indio_dev);
+ unsigned int scan_mask_len = iio_get_masklength(indio_dev);
u32 offset = 0;
u32 i;
int ret;
+ if (iio_trigger_using_own(indio_dev)) {
+ i = find_first_bit(indio_dev->active_scan_mask, scan_mask_len);
+ if (i >= scan_mask_len)
+ goto out;
+
+ ret = ads112c14_scan_read(data, (u8 *)&data->scan[0]);
+ if (ret) {
+ const struct iio_chan_spec *chan = &indio_dev->channels[i];
+
+ dev_err_once(indio_dev->dev.parent,
+ "failed to read channel %d: %pe; additional errors will be suppressed\n",
+ chan->channel, ERR_PTR(ret));
+ goto out;
+ }
+
+ iio_push_to_buffers_with_ts(indio_dev, data->scan,
+ sizeof(data->scan), pf->timestamp);
+ goto out;
+ }
+
iio_for_each_active_channel(indio_dev, i) {
const struct iio_chan_spec *chan = &indio_dev->channels[i];
@@ -992,6 +1023,89 @@ static const struct iio_info ads112c14_info = {
.read_label = ads112c14_read_label,
};
+static bool ads112c14_using_drdy_trigger(struct iio_dev *indio_dev)
+{
+ struct ads112c14_data *data = iio_priv(indio_dev);
+
+ return data->drdy_trig && indio_dev->trig == data->drdy_trig;
+}
+
+static bool ads112c14_validate_scan_mask(struct iio_dev *indio_dev,
+ const unsigned long *mask)
+{
+ if (!ads112c14_using_drdy_trigger(indio_dev))
+ return true;
+
+ return iio_validate_scan_mask_onehot(indio_dev, mask);
+}
+
+static int ads112c14_buffer_postenable(struct iio_dev *indio_dev)
+{
+ unsigned int scan_mask_len = iio_get_masklength(indio_dev);
+ struct ads112c14_data *data = iio_priv(indio_dev);
+ const struct iio_chan_spec *chan;
+ unsigned int i;
+ int ret;
+
+ if (!ads112c14_using_drdy_trigger(indio_dev))
+ return 0;
+
+ i = find_first_bit(indio_dev->active_scan_mask, scan_mask_len);
+ if (i >= scan_mask_len)
+ return -EINVAL;
+
+ chan = &indio_dev->channels[i];
+
+ guard(mutex)(&data->lock);
+
+ ret = ads112c14_prepare_channel(data, chan);
+ if (ret)
+ return ret;
+
+ ret = regmap_assign_bits(data->regmap, ADS112C14_REG_DEVICE_CFG,
+ ADS112C14_DEVICE_CFG_CONV_MODE,
+ ADS112C14_DEVICE_CFG_CONV_MODE_CONTINUOUS);
+ if (ret)
+ return ret;
+
+ ret = regmap_write(data->regmap, ADS112C14_REG_CONVERSION_CTRL,
+ ADS112C14_CONVERSION_CTRL_START);
+ if (ret) {
+ regmap_assign_bits(data->regmap, ADS112C14_REG_DEVICE_CFG,
+ ADS112C14_DEVICE_CFG_CONV_MODE,
+ ADS112C14_DEVICE_CFG_CONV_MODE_SINGLE_SHOT);
+ return ret;
+ }
+
+ return 0;
+}
+
+static int ads112c14_buffer_predisable(struct iio_dev *indio_dev)
+{
+ struct ads112c14_data *data = iio_priv(indio_dev);
+ int ret;
+
+ if (!ads112c14_using_drdy_trigger(indio_dev))
+ return 0;
+
+ guard(mutex)(&data->lock);
+
+ ret = regmap_write(data->regmap, ADS112C14_REG_CONVERSION_CTRL,
+ ADS112C14_CONVERSION_CTRL_STOP);
+ if (ret)
+ return ret;
+
+ return regmap_assign_bits(data->regmap, ADS112C14_REG_DEVICE_CFG,
+ ADS112C14_DEVICE_CFG_CONV_MODE,
+ ADS112C14_DEVICE_CFG_CONV_MODE_SINGLE_SHOT);
+}
+
+static const struct iio_buffer_setup_ops ads112c14_buffer_setup_ops = {
+ .postenable = ads112c14_buffer_postenable,
+ .predisable = ads112c14_buffer_predisable,
+ .validate_scan_mask = ads112c14_validate_scan_mask,
+};
+
static int ads112c14_populate_idac_mag(u32 current_nA, u8 *idac_mag)
{
u32 current_uA = current_nA / (NANO / MICRO);
@@ -1480,6 +1594,19 @@ static int ads112c14_probe(struct i2c_client *client)
0, dev_name(dev), indio_dev);
if (ret)
return ret;
+
+ data->drdy_trig = devm_iio_trigger_alloc(dev, "%s-dev%d-drdy",
+ info->name,
+ iio_device_id(indio_dev));
+ if (!data->drdy_trig)
+ return -ENOMEM;
+
+ data->drdy_trig->ops = &ads112c14_trigger_ops;
+ iio_trigger_set_drvdata(data->drdy_trig, indio_dev);
+
+ ret = devm_iio_trigger_register(dev, data->drdy_trig);
+ if (ret)
+ return ret;
}
ads112c14_populate_tables(data);
@@ -1490,7 +1617,8 @@ static int ads112c14_probe(struct i2c_client *client)
ret = devm_iio_triggered_buffer_setup(dev, indio_dev,
iio_pollfunc_store_time,
- ads112c14_trigger_handler, NULL);
+ ads112c14_trigger_handler,
+ &ads112c14_buffer_setup_ops);
if (ret)
return ret;
--
2.43.0
^ permalink raw reply related [flat|nested] 9+ messages in thread* Re: [PATCH v3 3/3] iio: adc: ti-ads112c14: add continuous mode support
2026-08-07 21:19 ` [PATCH v3 3/3] iio: adc: ti-ads112c14: add continuous mode support David Lechner (TI)
@ 2026-08-10 8:58 ` Andy Shevchenko
2026-08-16 20:26 ` Jonathan Cameron
1 sibling, 0 replies; 9+ messages in thread
From: Andy Shevchenko @ 2026-08-10 8:58 UTC (permalink / raw)
To: David Lechner (TI)
Cc: Jonathan Cameron, Nuno Sá, Andy Shevchenko, Chris Hall,
Patrick Edwards, Kurt Borja, linux-iio, linux-kernel
On Fri, Aug 07, 2026 at 04:19:48PM -0500, David Lechner (TI) wrote:
> Add support for continuous mode in the TI ADS112C14 ADC driver. In this
> mode the ADC itself is starting each conversion, so we add a trigger
> based on the DRDY interrupt to read each sample. This mode is also
> limited in that only one channel can be enabled at a time since the
> chip does not have a sequencer or simultaneous sampling capability.
> Continuous mode will only be used when this new trigger is the current
> trigger.
...
> static irqreturn_t ads112c14_trigger_handler(int irq, void *private)
> struct iio_poll_func *pf = private;
> struct iio_dev *indio_dev = pf->indio_dev;
> struct ads112c14_data *data = iio_priv(indio_dev);
> + unsigned int scan_mask_len = iio_get_masklength(indio_dev);
This is from indio_dev, which is defined two lines up, so this, longer one, can
be bumped one line up.
> u32 offset = 0;
> u32 i;
> int ret;
>
> + if (iio_trigger_using_own(indio_dev)) {
> + i = find_first_bit(indio_dev->active_scan_mask, scan_mask_len);
> + if (i >= scan_mask_len)
'>' is redundant, '==' suffices.
> + goto out;
> +
> + ret = ads112c14_scan_read(data, (u8 *)&data->scan[0]);
> + if (ret) {
> + const struct iio_chan_spec *chan = &indio_dev->channels[i];
> +
> + dev_err_once(indio_dev->dev.parent,
> + "failed to read channel %d: %pe; additional errors will be suppressed\n",
> + chan->channel, ERR_PTR(ret));
> + goto out;
> + }
> +
> + iio_push_to_buffers_with_ts(indio_dev, data->scan,
> + sizeof(data->scan), pf->timestamp);
> + goto out;
> + }
...
> +static int ads112c14_buffer_postenable(struct iio_dev *indio_dev)
> +{
> + unsigned int scan_mask_len = iio_get_masklength(indio_dev);
> + struct ads112c14_data *data = iio_priv(indio_dev);
> + const struct iio_chan_spec *chan;
> + unsigned int i;
> + int ret;
> +
> + if (!ads112c14_using_drdy_trigger(indio_dev))
> + return 0;
> + i = find_first_bit(indio_dev->active_scan_mask, scan_mask_len);
> + if (i >= scan_mask_len)
> + return -EINVAL;
> +
> + chan = &indio_dev->channels[i];
These lines repeat what you have in ads112c14_trigger_handler(). Perhaps
a helper to return a channel or error pointer or NULL?
> + guard(mutex)(&data->lock);
> +
> + ret = ads112c14_prepare_channel(data, chan);
> + if (ret)
> + return ret;
> +
> + ret = regmap_assign_bits(data->regmap, ADS112C14_REG_DEVICE_CFG,
> + ADS112C14_DEVICE_CFG_CONV_MODE,
> + ADS112C14_DEVICE_CFG_CONV_MODE_CONTINUOUS);
> + if (ret)
> + return ret;
> +
> + ret = regmap_write(data->regmap, ADS112C14_REG_CONVERSION_CTRL,
> + ADS112C14_CONVERSION_CTRL_START);
> + if (ret) {
> + regmap_assign_bits(data->regmap, ADS112C14_REG_DEVICE_CFG,
> + ADS112C14_DEVICE_CFG_CONV_MODE,
> + ADS112C14_DEVICE_CFG_CONV_MODE_SINGLE_SHOT);
> + return ret;
> + }
> +
> + return 0;
> +}
--
With Best Regards,
Andy Shevchenko
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [PATCH v3 3/3] iio: adc: ti-ads112c14: add continuous mode support
2026-08-07 21:19 ` [PATCH v3 3/3] iio: adc: ti-ads112c14: add continuous mode support David Lechner (TI)
2026-08-10 8:58 ` Andy Shevchenko
@ 2026-08-16 20:26 ` Jonathan Cameron
1 sibling, 0 replies; 9+ messages in thread
From: Jonathan Cameron @ 2026-08-16 20:26 UTC (permalink / raw)
To: David Lechner (TI)
Cc: Nuno Sá, Andy Shevchenko, Chris Hall, Patrick Edwards,
Kurt Borja, linux-iio, linux-kernel
On Fri, 07 Aug 2026 16:19:48 -0500
"David Lechner (TI)" <dlechner@baylibre.com> wrote:
> Add support for continuous mode in the TI ADS112C14 ADC driver. In this
> mode the ADC itself is starting each conversion, so we add a trigger
> based on the DRDY interrupt to read each sample. This mode is also
> limited in that only one channel can be enabled at a time since the
> chip does not have a sequencer or simultaneous sampling capability.
> Continuous mode will only be used when this new trigger is the current
> trigger.
>
> Signed-off-by: David Lechner (TI) <dlechner@baylibre.com>
Hi David,
regmap_assign_bits() usage here is a bit odd.
It is just a bool taking wrapper around set_bits and clear_bits.
It 'works' here because the values are 0 and 1.
There isn't a natural bool for these two modes, so to make this look right
you'd end up with something like:
ADS112C14_DEVICE_CFG_CONV_MODE_SINGLE_NOT_CONT
and that is horrible. So I'd just use FIELD_PREP() and definitions
for the two values.
Otherwise looks fine to me.
J
> +
> +static int ads112c14_buffer_predisable(struct iio_dev *indio_dev)
> +{
> + struct ads112c14_data *data = iio_priv(indio_dev);
> + int ret;
> +
> + if (!ads112c14_using_drdy_trigger(indio_dev))
> + return 0;
> +
> + guard(mutex)(&data->lock);
> +
> + ret = regmap_write(data->regmap, ADS112C14_REG_CONVERSION_CTRL,
> + ADS112C14_CONVERSION_CTRL_STOP);
> + if (ret)
> + return ret;
> +
> + return regmap_assign_bits(data->regmap, ADS112C14_REG_DEVICE_CFG,
> + ADS112C14_DEVICE_CFG_CONV_MODE,
> + ADS112C14_DEVICE_CFG_CONV_MODE_SINGLE_SHOT);
This looks odd as last parameter that takes is a boolean.
I think you just want an update_bits + appropriate FIELD_PREP()
> +}
> +
> +static const struct iio_buffer_setup_ops ads112c14_buffer_setup_ops = {
> + .postenable = ads112c14_buffer_postenable,
> + .predisable = ads112c14_buffer_predisable,
> + .validate_scan_mask = ads112c14_validate_scan_mask,
> +};
> +
> static int ads112c14_populate_idac_mag(u32 current_nA, u8 *idac_mag)
> {
> u32 current_uA = current_nA / (NANO / MICRO);
> @@ -1480,6 +1594,19 @@ static int ads112c14_probe(struct i2c_client *client)
> 0, dev_name(dev), indio_dev);
> if (ret)
> return ret;
> +
> + data->drdy_trig = devm_iio_trigger_alloc(dev, "%s-dev%d-drdy",
> + info->name,
> + iio_device_id(indio_dev));
> + if (!data->drdy_trig)
> + return -ENOMEM;
> +
> + data->drdy_trig->ops = &ads112c14_trigger_ops;
> + iio_trigger_set_drvdata(data->drdy_trig, indio_dev);
> +
> + ret = devm_iio_trigger_register(dev, data->drdy_trig);
> + if (ret)
> + return ret;
> }
>
> ads112c14_populate_tables(data);
> @@ -1490,7 +1617,8 @@ static int ads112c14_probe(struct i2c_client *client)
>
> ret = devm_iio_triggered_buffer_setup(dev, indio_dev,
> iio_pollfunc_store_time,
> - ads112c14_trigger_handler, NULL);
> + ads112c14_trigger_handler,
> + &ads112c14_buffer_setup_ops);
> if (ret)
> return ret;
>
>
^ permalink raw reply [flat|nested] 9+ messages in thread