Re: [PATCH v2 3/3] iio: accel: adxl367: add support for INT2 interrupt pin
Nuno Sá <[email protected]>
| Newsgroups | org.kernel.vger.linux-iio,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178671050969.21598.13163934753300429850.b4-review@b4> |
On Thu, 13 Aug 2026 11:14:52 +0300, Antoniu Miclaus <[email protected]> wrote: > diff --git a/drivers/iio/accel/adxl367.c b/drivers/iio/accel/adxl367.c > index 8c3de11a10a3..df385740b17b 100644 > --- a/drivers/iio/accel/adxl367.c > +++ b/drivers/iio/accel/adxl367.c > @@ -1426,6 +1430,31 @@ static int adxl367_setup(struct adxl367_state *st) > return adxl367_set_measure_en(st, true); > } > > +static int adxl367_set_int_map_reg(struct adxl367_state *st) > +{ > + int irq; > + > + irq = fwnode_irq_get_byname(dev_fwnode(st->dev), "INT1"); > + if (irq == -EPROBE_DEFER) > + return irq; > + if (irq > 0) { > + st->int_map_reg = ADXL367_REG_INT1_MAP; > + return 0; sashiko point is sensible but I guess both INT ouputs are pretty much the same? So even even if there's a mismatch against spi/i2c I guess it is not problematic? - Nuno Sá -- Nuno Sá <[email protected]>