mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: rodrigo.alencar@analog.com
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux@analog.com, devicetree@vger.kernel.org,
	linux-pwm@vger.kernel.org,  linux-doc@vger.kernel.org,
	Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>,
	 Olivier Moysan <olivier.moysan@foss.st.com>,
	Jonathan Cameron <jic23@kernel.org>,
	 David Lechner <dlechner@baylibre.com>,
	Andy Shevchenko <andy@kernel.org>,
	 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>,
	Shuah Khan <skhan@linuxfoundation.org>,
	 Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 07/10] iio: frequency: ad9910: support drctl control
Date: Tue, 20 Oct 2026 14:23:41 +0200	[thread overview]
Message-ID: <atdcOsaDbtaQJd-9@monoceros> (raw)
In-Reply-To: <20261015-ad9910-backend-support-v1-7-3c21648c8e26@analog.com>

[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]

On Thu, Oct 15, 2026 at 01:49:47PM -0300, Rodrigo Alencar via B4 Relay wrote:
> +static int ad9910_drctl_sync(struct ad9910_state *st)
> +{
> +	struct pwm_state state;
> +	bool ndh, ndl;
> +	int ret;
> +
> +	if (!st->drctl_pwm)
> +		return 0;
> +
> +	ndh = FIELD_GET(AD9910_CFR2_DRG_NO_DWELL_HIGH_MSK,
> +			st->reg[AD9910_REG_CFR2].val32);
> +	ndl = FIELD_GET(AD9910_CFR2_DRG_NO_DWELL_LOW_MSK,
> +			st->reg[AD9910_REG_CFR2].val32);
> +
> +	pwm_init_state(st->drctl_pwm, &state);
> +
> +	if (!ndh && ndl) {
> +		state.duty_cycle = st->ramp_down_time_ns / 2;
> +		state.period = st->ramp_down_time_ns;
> +		state.polarity = PWM_POLARITY_INVERSED;
> +	} else if (ndh && !ndl) {
> +		state.duty_cycle = st->ramp_up_time_ns / 2;
> +		state.period = st->ramp_up_time_ns;
> +		state.polarity = PWM_POLARITY_NORMAL;
> +	} else if (!ndh && !ndl) {
> +		state.duty_cycle = st->ramp_up_time_ns;
> +		state.period = st->ramp_up_time_ns + st->ramp_down_time_ns;
> +		state.polarity = PWM_POLARITY_NORMAL;
> +	} else {
> +		state.duty_cycle = 0;
> +		state.period = st->ramp_up_time_ns + st->ramp_down_time_ns;
> +		state.polarity = PWM_POLARITY_NORMAL;
> +	}
> +
> +	if (!state.period) {
> +		pwm_disable(st->drctl_pwm);
> +		return 0;
> +	}
> +
> +	state.enabled = true;
> +	ret = pwm_apply_might_sleep(st->drctl_pwm, &state);
> +	if (ret)
> +		return ret;
> +
> +	ret = pwm_get_state_hw(st->drctl_pwm, &state);
> +	if (ret)
> +		return ret;

Does enabling the PWM have any side effects? Are you doing that only to
be able to call pwm_get_state_hw() and thus find out what the resulting
output looks like? In that case, pwm_round_waveform_might_sleep() might
be your friend.

> +
> +	if (!ndh && ndl) {
> +		st->ramp_down_time_ns = state.period;
> +	} else if (ndh && !ndl) {
> +		st->ramp_up_time_ns = state.period;
> +	} else if (!ndh && !ndl) {
> +		st->ramp_up_time_ns = state.duty_cycle;
> +		st->ramp_down_time_ns = state.period - st->ramp_up_time_ns;
> +	}

So the configuration depends on the previous state of the
AD9910_REG_CFR2 register? That's a recipe for surprises?!

> +
> +	return 0;
> +}
> +

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2026-10-20 12:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 16:49 [PATCH 00/10] iio: frequency: ad9910: add IIO backend support Rodrigo Alencar via B4 Relay
2026-10-15 16:49 ` [PATCH 01/10] iio: frequency: ad9910: powerdown fix Rodrigo Alencar via B4 Relay
2026-10-16  9:22   ` Nuno Sá
2026-10-15 16:49 ` [PATCH 02/10] iio: backend: add devm_iio_backend_get_optional() Rodrigo Alencar via B4 Relay
2026-10-15 18:41   ` Andy Shevchenko
2026-10-16  8:45     ` Nuno Sá
2026-10-16 11:18       ` Rodrigo Alencar
2026-10-16 13:01         ` Nuno Sá
2026-10-16 13:21           ` Andy Shevchenko
2026-10-16 13:19         ` Andy Shevchenko
2026-10-16 13:32           ` Rodrigo Alencar
2026-10-16 14:07           ` Nuno Sá
2026-10-17 20:28             ` Jonathan Cameron
2026-10-19  6:07               ` Nuno Sá
2026-10-16  8:46   ` Nuno Sá
2026-10-15 16:49 ` [PATCH 03/10] dt-bindings: iio: frequency: add adi,ad9910-axi-backend Rodrigo Alencar via B4 Relay
2026-10-15 18:59   ` Conor Dooley
2026-10-15 16:49 ` [PATCH 04/10] dt-bindings: iio: frequency: ad9910: add io-backends property Rodrigo Alencar via B4 Relay
2026-10-15 19:00   ` Conor Dooley
2026-10-15 16:49 ` [PATCH 05/10] iio: frequency: ad9910: move channel indexes into a shared header Rodrigo Alencar via B4 Relay
2026-10-16  9:22   ` Nuno Sá
2026-10-15 16:49 ` [PATCH 06/10] iio: frequency: ad9910: add axi backend driver Rodrigo Alencar via B4 Relay
2026-10-16  9:22   ` Nuno Sá
2026-10-20 12:39   ` Uwe Kleine-König
2026-10-15 16:49 ` [PATCH 07/10] iio: frequency: ad9910: support drctl control Rodrigo Alencar via B4 Relay
2026-10-16  9:22   ` Nuno Sá
2026-10-20 12:23   ` Uwe Kleine-König [this message]
2026-10-20 12:43     ` Rodrigo Alencar
2026-10-15 16:49 ` [PATCH 08/10] iio: frequency: ad9910: support iio backend Rodrigo Alencar via B4 Relay
2026-10-16  9:22   ` Nuno Sá
2026-10-17 20:39   ` Jonathan Cameron
2026-10-15 16:49 ` [PATCH 09/10] iio: ABI: add integration_time for output channels Rodrigo Alencar via B4 Relay
2026-10-15 18:38   ` Andy Shevchenko
2026-10-16  9:22   ` Nuno Sá
2026-10-17 20:43   ` Jonathan Cameron
2026-10-15 16:49 ` [PATCH 10/10] docs: iio: ad9910: document DRCTL pin control Rodrigo Alencar via B4 Relay

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=atdcOsaDbtaQJd-9@monoceros \
    --to=ukleinek@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=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=jonathan.cameron@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux@analog.com \
    --cc=olivier.moysan@foss.st.com \
    --cc=rdunlap@infradead.org \
    --cc=robh@kernel.org \
    --cc=rodrigo.alencar@analog.com \
    --cc=skhan@linuxfoundation.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

all inboxes | Powered by JetHome®