From: Jonathan Cameron <jic23@kernel.org>
To: Rodrigo Alencar via B4 Relay
<devnull+rodrigo.alencar.analog.com@kernel.org>
Cc: rodrigo.alencar@analog.com, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v3 3/6] iio: frequency: adf41513: handle LE synchronization feature
Date: Sun, 11 Jan 2026 13:58:29 +0000 [thread overview]
Message-ID: <20260111135829.3863cf1c@jic23-huawei> (raw)
In-Reply-To: <20260108-adf41513-iio-driver-v3-3-23d1371aef48@analog.com>
On Thu, 08 Jan 2026 12:14:52 +0000
Rodrigo Alencar via B4 Relay <devnull+rodrigo.alencar.analog.com@kernel.org> wrote:
> From: Rodrigo Alencar <rodrigo.alencar@analog.com>
>
> When LE sync is enabled, it is must be set after powering up and must be
> disabled when powering down. It is recommended when using the PLL as
> a frequency synthesizer, where reference signal will always be present
> while the device is being configured.
>
> Signed-off-by: Rodrigo Alencar <rodrigo.alencar@analog.com>
Hi Rodrigo,
A few comments inline.
> ---
> drivers/iio/frequency/adf41513.c | 32 +++++++++++++++++++++++++++++---
> 1 file changed, 29 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/frequency/adf41513.c b/drivers/iio/frequency/adf41513.c
> index 69dcbbc1f393..0cdf24989c93 100644
> --- a/drivers/iio/frequency/adf41513.c
> +++ b/drivers/iio/frequency/adf41513.c
> @@ -220,6 +220,7 @@ struct adf41513_data {
> bool phase_detector_polarity;
>
> bool logic_lvl_1v8_en;
> + bool le_sync_en;
> };
>
> struct adf41513_pll_settings {
> @@ -697,13 +698,25 @@ static int adf41513_set_frequency(struct adf41513_state *st, u64 freq_uhz, u16 s
> static int adf41513_suspend(struct adf41513_state *st)
> {
> st->regs[ADF41513_REG6] |= FIELD_PREP(ADF41513_REG6_POWER_DOWN_MSK, 1);
> + st->regs[ADF41513_REG12] &= ~ADF41513_REG12_LE_SELECT_MSK;
> return adf41513_sync_config(st, ADF41513_SYNC_DIFF);
> }
>
> static int adf41513_resume(struct adf41513_state *st)
> {
> + int ret;
> +
> st->regs[ADF41513_REG6] &= ~ADF41513_REG6_POWER_DOWN_MSK;
> - return adf41513_sync_config(st, ADF41513_SYNC_DIFF);
> + ret = adf41513_sync_config(st, ADF41513_SYNC_DIFF);
> + if (ret < 0)
If you know it is either 0 for good or less than zero, prefer
if (ret) (for reason that follows)
> + return ret;
> +
> + if (st->data.le_sync_en) {
> + st->regs[ADF41513_REG12] |= ADF41513_REG12_LE_SELECT_MSK;
> + ret = adf41513_sync_config(st, ADF41513_SYNC_DIFF);
Similar to below - I'd like to see
if (ret)
return ret;
here to avoid returning stale parameter from above (which might be postive
based on local code).
> + }
> +
> + return ret;
> }
>
> static ssize_t adf41513_read_uhz(struct iio_dev *indio_dev,
> @@ -994,6 +1007,8 @@ static int adf41513_parse_fw(struct adf41513_state *st)
> st->data.lock_detect_count = tmp;
> }
>
> + /* load enable sync */
> + st->data.le_sync_en = device_property_read_bool(dev, "adi,le-sync-enable");
> st->data.freq_resolution_uhz = MICROHZ_PER_HZ;
>
> return 0;
> @@ -1001,6 +1016,7 @@ static int adf41513_parse_fw(struct adf41513_state *st)
>
> static int adf41513_setup(struct adf41513_state *st)
> {
> + int ret;
> u32 tmp;
>
> memset(st->regs_hw, 0xFF, sizeof(st->regs_hw));
> @@ -1034,8 +1050,18 @@ static int adf41513_setup(struct adf41513_state *st)
> st->data.logic_lvl_1v8_en ? 0 : 1);
>
> /* perform initialization sequence with power-up frequency */
> - return adf41513_set_frequency(st, st->data.power_up_frequency_hz * MICROHZ_PER_HZ,
> - ADF41513_SYNC_ALL);
> + ret = adf41513_set_frequency(st,
> + st->data.power_up_frequency_hz * MICROHZ_PER_HZ,
> + ADF41513_SYNC_ALL);
> + if (ret < 0)
if (ret)
assuming set_frequency never returns a positive.
> + return ret;
> +
> + if (st->data.le_sync_en) {
> + st->regs[ADF41513_REG12] |= ADF41513_REG12_LE_SELECT_MSK;
> + ret = adf41513_sync_config(st, ADF41513_SYNC_DIFF);
Slightly preference for
if (ret)
return ret;
}
return 0;
Because otherwise a 'stale' (though it is zero) return value is used and that sort
of code pattern tends to be a little fragile and hard to read.
> + }
> +
> + return ret;
> }
>
> static void adf41513_power_down(void *data)
>
next prev parent reply other threads:[~2026-01-11 13:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 12:14 [PATCH v3 0/6] ADF41513/ADF41510 PLL frequency synthesizers Rodrigo Alencar via B4 Relay
2026-01-08 12:14 ` [PATCH v3 1/6] dt-bindings: iio: frequency: add adf41513 Rodrigo Alencar via B4 Relay
2026-01-09 8:13 ` Krzysztof Kozlowski
2026-01-12 10:04 ` Rodrigo Alencar
2026-01-12 16:32 ` Krzysztof Kozlowski
2026-01-08 12:14 ` [PATCH v3 2/6] iio: frequency: adf41513: driver implementation Rodrigo Alencar via B4 Relay
2026-01-09 18:55 ` Andy Shevchenko
2026-01-12 9:56 ` Rodrigo Alencar
2026-01-12 10:57 ` Andy Shevchenko
2026-01-13 9:32 ` Rodrigo Alencar
2026-01-16 11:31 ` Rodrigo Alencar
2026-01-16 13:50 ` Andy Shevchenko
2026-01-16 13:53 ` Andy Shevchenko
2026-01-11 13:53 ` Jonathan Cameron
2026-01-08 12:14 ` [PATCH v3 3/6] iio: frequency: adf41513: handle LE synchronization feature Rodrigo Alencar via B4 Relay
2026-01-11 13:58 ` Jonathan Cameron [this message]
2026-01-08 12:14 ` [PATCH v3 4/6] iio: frequency: adf41513: features on frequency change Rodrigo Alencar via B4 Relay
2026-01-09 19:07 ` Andy Shevchenko
2026-01-12 9:45 ` Rodrigo Alencar
2026-01-12 10:54 ` Andy Shevchenko
2026-01-16 17:57 ` Jonathan Cameron
2026-01-19 7:38 ` Andy Shevchenko
2026-01-19 10:41 ` Jonathan Cameron
2026-01-19 13:18 ` Andy Shevchenko
2026-01-08 12:14 ` [PATCH v3 5/6] docs: iio: add documentation for adf41513 driver Rodrigo Alencar via B4 Relay
2026-01-08 12:14 ` [PATCH v3 6/6] Documentation: ABI: testing: add common ABI file for iio/frequency Rodrigo Alencar via B4 Relay
2026-01-11 14:01 ` Jonathan Cameron
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=20260111135829.3863cf1c@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=devnull+rodrigo.alencar.analog.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rodrigo.alencar@analog.com \
/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