From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Fenglin Wu <fenglin.wu@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, Lee Jones <lee@kernel.org>,
Pavel Machek <pavel@kernel.org>
Cc: David Collins <david.collins@oss.qualcomm.com>,
Subbaraman Narayanamurthy
<subbaraman.narayanamurthy@oss.qualcomm.com>,
Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: rgb: leds-qcom-lpg: Add PWM frequency mode support
Date: Fri, 31 Jul 2026 16:20:50 +0200 [thread overview]
Message-ID: <7a0c4a70-b838-4c7c-9f16-d394ffef95ba@oss.qualcomm.com> (raw)
In-Reply-To: <20260729-lpg-pwm-fm-support-v1-1-16d3c72a9921@oss.qualcomm.com>
On 7/29/26 11:48 AM, Fenglin Wu wrote:
> Certain PWM channels on a PMIC (e.g. PM8350C PWM4) support a Frequency
> Mode (FM) that can generate waveforms with more frequency points than
> the standard LPG PWM mode. The trade-off is that the duty cycle can
> only be fixed at 50%. Add the FM support. When the PWM channel is
> requested to set a duty cycle to exactly 50%, use FM mode by default
> as it provides a finer-grained frequency resolution in that case.
>
> Signed-off-by: Fenglin Wu <fenglin.wu@oss.qualcomm.com>
> ---
[...]
> + for (clk = 1; clk < clk_len; clk++) {
> + last_err = U64_MAX;
> +
> + for (exp = 0; exp <= LPG_MAX_M; exp++) {
> + /* Calculate pwm_value_lsb for this (clk, exp) pair */
> + lsb_tmp = period_ns;
> + lsb_tmp = div64_u64(lsb_tmp, clk_period_arr[clk]);
> + lsb_tmp >>= (exp + 1);
> +
> + if (lsb_tmp == 0 || lsb_tmp - 1 > U8_MAX)
> + continue;
> +
> + lsb = lsb_tmp - 1;
> +
> + period_actual = (u64)(lsb + 1);
Did you mean `(u64)(lsb) + 1` here?
[...]
> + /* Calculate actual period for reference */
> + period_actual = (u64)(best_lsb + 1);
And here too?
In general, I think there's nothing that prevents you from
turning all of these variables into u64s
[...]
> regmap_read(lpg->map, chan->base + LPG_SUBTYPE_REG, &chan->subtype);
> + if (data->channels[i].fm_capable) {
> + ret = regmap_read(lpg->map, chan->base + PWM_STATUS1_REG, &status);
> + if (ret < 0)
> + return ret;
> +
> + chan->fm_capable = !!(status & PWM_FM_PRESENT);
Can we read this register blindly by chance and drop the match data?
Konrad
next prev parent reply other threads:[~2026-07-31 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 9:48 Fenglin Wu
2026-07-31 14:20 ` Konrad Dybcio [this message]
2026-08-03 1:50 ` Fenglin Wu
2026-09-03 7:24 ` Konrad Dybcio
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=7a0c4a70-b838-4c7c-9f16-d394ffef95ba@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=david.collins@oss.qualcomm.com \
--cc=fenglin.wu@oss.qualcomm.com \
--cc=kamal.wadhwa@oss.qualcomm.com \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=subbaraman.narayanamurthy@oss.qualcomm.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
all inboxes | Powered by JetHome®