From: "Kurt Borja" <kuurtb@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>, "Kurt Borja" <kuurtb@gmail.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/7] iio: adc: ti-ads1262: Add excitation current support
Date: Tue, 30 Jun 2026 12:18:38 -0500 [thread overview]
Message-ID: <DJMK080GOMNP.1K9VX4CMRQKL4@gmail.com> (raw)
In-Reply-To: <20260630014723.786a8885@jic23-huawei>
On Mon Jun 29, 2026 at 7:47 PM -05, Jonathan Cameron wrote:
> On Sun, 28 Jun 2026 00:36:05 -0500
> Kurt Borja <kuurtb@gmail.com> wrote:
>
>> Support the two IDAC excitation current sources. Each channel can route
>> its IDAC1/IDAC2 outputs to a pin via the "excitation-channels" property
>> and select a magnitude via "excitation-current-nanoamp".
>>
>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>> ---
>> drivers/iio/adc/ti-ads1262.c | 78 ++++++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 76 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/iio/adc/ti-ads1262.c b/drivers/iio/adc/ti-ads1262.c
>> index ece97a0c2b1304ad..8921eaae537f6b0a 100644
>> --- a/drivers/iio/adc/ti-ads1262.c
>> +++ b/drivers/iio/adc/ti-ads1262.c
>> @@ -193,6 +193,22 @@ enum {
>> ADS1262_INPMUX_LAST
>> };
>>
>> +enum {
>> + ADS1262_IDACMUX_AIN0,
>> + ADS1262_IDACMUX_AIN1,
>> + ADS1262_IDACMUX_AIN2,
>> + ADS1262_IDACMUX_AIN3,
>> + ADS1262_IDACMUX_AIN4,
>> + ADS1262_IDACMUX_AIN5,
>> + ADS1262_IDACMUX_AIN6,
>> + ADS1262_IDACMUX_AIN7,
>> + ADS1262_IDACMUX_AIN8,
>> + ADS1262_IDACMUX_AIN9,
>> + ADS1262_IDACMUX_AINCOM,
>> + ADS1262_IDACMUX_NO_CONN,
>> + ADS1262_IDACMUX_LAST
>
> _LAST usually means inclusive. So probably call this NUM or something like that
> to show that it should be one more than last value.
>
>> +};
>
>> @@ -450,7 +468,7 @@ static int ads1262_dev_read_by_cmd(struct ads1262 *st, u8 cmd, __be32 *val)
>> static int ads1262_channel_enable(struct ads1262 *st,
>> struct ads1262_channel *chan)
>> {
>> - u8 mode0, mode1, mode2, inpmux, refmux;
>> + u8 mode0, mode1, mode2, inpmux, idacmux, idacmag, refmux;
>> int ret;
>>
>> /* Avoid using guard() here to mitigate AB/BA deadlock warning */
>> @@ -464,6 +482,10 @@ static int ads1262_channel_enable(struct ads1262 *st,
>> FIELD_PREP(ADS1262_MODE2_BYPASS_MASK, chan->pga_bypass);
>> inpmux = FIELD_PREP(ADS1262_INPMUX_MUXN_MASK, chan->input[1]) |
>> FIELD_PREP(ADS1262_INPMUX_MUXP_MASK, chan->input[0]);
>> + idacmux = FIELD_PREP(ADS1262_IDACMUX_MUX1_MASK, chan->idac_mux[0]) |
>> + FIELD_PREP(ADS1262_IDACMUX_MUX2_MASK, chan->idac_mux[1]);
>> + idacmag = FIELD_PREP(ADS1262_IDACMAG_MAG1_MASK, chan->idac_mag[0]) |
>> + FIELD_PREP(ADS1262_IDACMAG_MAG2_MASK, chan->idac_mag[1]);
>
> This presumably feeds into the discussion of locking that you were having
> with David, but I'd find this a lot easier to read if these were just
> above where the values are used. Then we can clearly see the match between
> masks and fields. If you have to do it like this, then add variables up
> here for the masks as well.
I'll move them above each regmap calls after reorganizing the locking
stuff.
>
>
>> refmux = FIELD_PREP(ADS1262_REFMUX_RMUXN_MASK, chan->reference[1]) |
>> FIELD_PREP(ADS1262_REFMUX_RMUXP_MASK, chan->reference[0]);
>> mutex_unlock(&st->chan_lock);
--
Thanks,
~ Kurt
next prev parent reply other threads:[~2026-06-30 17:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 5:36 [PATCH v2 0/7] iio: adc: Add TI ADS126X ADC family support Kurt Borja
2026-06-28 5:36 ` [PATCH v2 1/7] dt-bindings: iio: adc: Add TI ADS126x ADC family Kurt Borja
2026-06-28 15:45 ` David Lechner
2026-06-28 19:12 ` Kurt Borja
2026-06-29 14:21 ` David Lechner
2026-06-29 16:27 ` Kurt Borja
2026-06-29 16:43 ` David Lechner
2026-06-30 17:14 ` Kurt Borja
2026-06-30 18:38 ` David Lechner
2026-07-01 0:28 ` Jonathan Cameron
2026-06-28 5:36 ` [PATCH v2 2/7] iio: adc: Add ti-ads1262 driver Kurt Borja
2026-06-28 17:15 ` David Lechner
2026-06-28 20:00 ` Kurt Borja
2026-06-29 14:38 ` David Lechner
2026-06-30 0:32 ` Jonathan Cameron
2026-06-30 17:17 ` Kurt Borja
2026-06-30 0:28 ` Jonathan Cameron
2026-06-30 0:43 ` Jonathan Cameron
2026-06-28 5:36 ` [PATCH v2 3/7] iio: adc: ti-ads1262: Add channel filter support Kurt Borja
2026-06-28 5:36 ` [PATCH v2 4/7] iio: adc: ti-ads1262: Add excitation current support Kurt Borja
2026-06-30 0:47 ` Jonathan Cameron
2026-06-30 17:18 ` Kurt Borja [this message]
2026-06-28 5:36 ` [PATCH v2 5/7] iio: adc: ti-ads1262: Add conversion delay support Kurt Borja
2026-06-30 0:50 ` Jonathan Cameron
2026-06-30 17:23 ` Kurt Borja
2026-06-30 18:44 ` David Lechner
2026-07-01 0:20 ` Jonathan Cameron
2026-06-28 5:36 ` [PATCH v2 6/7] iio: adc: ti-ads1262: Add buffer and trigger support Kurt Borja
2026-06-30 0:54 ` Jonathan Cameron
2026-06-28 5:36 ` [PATCH v2 7/7] iio: adc: Add ti-ads1263-adc2 driver Kurt Borja
2026-06-28 17:22 ` David Lechner
2026-06-28 20:08 ` Kurt Borja
2026-06-29 16:38 ` David Lechner
2026-06-30 1:00 ` Jonathan Cameron
2026-06-30 17:57 ` Kurt Borja
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=DJMK080GOMNP.1K9VX4CMRQKL4@gmail.com \
--to=kuurtb@gmail.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.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