From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Petar Stepanovic <pstepanovic@axiado.com>
Cc: "Akhila Kavi" <akavi@axiado.com>,
"Prasad Bolisetty" <pbolisetty@axiado.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>,
"Harshit Shah" <hshah@axiado.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] iio: adc: add Axiado SARADC driver
Date: Fri, 17 Jul 2026 11:38:42 +0300 [thread overview]
Message-ID: <alnqEnVm9rGTapFB@ashevche-desk.local> (raw)
In-Reply-To: <alnpMFK6_ZkdWlLi@ashevche-desk.local>
On Fri, Jul 17, 2026 at 11:35:01AM +0300, Andy Shevchenko wrote:
> On Thu, Jul 16, 2026 at 10:53:02PM -0700, Petar Stepanovic wrote:
...
> > +static void axiado_saradc_disable(void *data)
> > +{
> > + struct axiado_saradc *info = data;
> > +
> > + regmap_write(info->regmap, AX_SARADC_GLOBAL_CTRL_REG,
> > + AX_SARADC_GLOBAL_CTRL_PD);
> > +}
>
> Supply regmap instead of info and make this simpler
>
> static void axiado_saradc_disable(void *map)
> {
> regmap_write(map, AX_SARADC_GLOBAL_CTRL_REG, AX_SARADC_GLOBAL_CTRL_PD);
> }
>
> ...
>
> > + regval = FIELD_PREP(AX_SARADC_GLOBAL_CTRL_CH_EN_MASK,
> > + GENMASK(soc_data->num_channels - 1, 0)) |
> > + AX_SARADC_GLOBAL_CTRL_SAMPLE_16 |
> > + AX_SARADC_GLOBAL_CTRL_MODE_MANUAL |
> > + AX_SARADC_GLOBAL_CTRL_ENABLE;
>
> This is not used in the below call, move it closer to its user.
>
> > + ret = regmap_write(info->regmap, AX_SARADC_GLOBAL_CTRL_REG,
> > + AX_SARADC_GLOBAL_CTRL_PD);
>
> With
>
> struct regmap *map;
>
> at the top, this and other will be shorter and easier to follow.
> And I would dare to use a single line:
>
> ret = regmap_write(map, AX_SARADC_GLOBAL_CTRL_REG, AX_SARADC_GLOBAL_CTRL_PD);
Looking closer at this I think it's a leftover? Since it's an action that does
disable. This one should only enable chip, right?
> > + if (ret)
> > + return ret;
> > +
> > + ret = regmap_write(info->regmap, AX_SARADC_GLOBAL_CTRL_REG, regval);
> > + if (ret)
> > + return ret;
>
> > + ret = devm_add_action_or_reset(dev, axiado_saradc_disable, info);
>
> ret = devm_add_action_or_reset(dev, axiado_saradc_disable, map);
>
> > + if (ret)
> > + return ret;
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-07-17 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 5:53 [PATCH v4 0/2] iio: adc: Add Axiado SARADC driver Petar Stepanovic
2026-07-17 5:53 ` [PATCH v4 1/2] dt-bindings: iio: adc: add Axiado AX3000/AX3005 SARADC Petar Stepanovic
2026-07-17 5:53 ` [PATCH v4 2/2] iio: adc: add Axiado SARADC driver Petar Stepanovic
2026-07-17 8:34 ` Andy Shevchenko
2026-07-17 8:38 ` Andy Shevchenko [this message]
2026-07-18 1:40 ` Jonathan Cameron
2026-07-18 13:51 ` Uwe Kleine-König
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=alnqEnVm9rGTapFB@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=akavi@axiado.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=hshah@axiado.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=pbolisetty@axiado.com \
--cc=pstepanovic@axiado.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