From: Linus Walleij <linusw@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Input: isa1200 - new driver for Imagis ISA1200
Date: Thu, 30 Apr 2026 11:22:29 +0200 [thread overview]
Message-ID: <CAD++jLkU-G38xtzzfAV_otiYuM2G5NHdCdtjFjsy2AjpG22_rg@mail.gmail.com> (raw)
In-Reply-To: <20260428114308.113253-3-clamor95@gmail.com>
Hi Svyatoslav,
I just saw this thing:
On Tue, Apr 28, 2026 at 1:43 PM Svyatoslav Ryhel <clamor95@gmail.com> wrote:
> +/* HCTRL5 controls the PWM high duty cycle of internal channel */
> +#define ISA1200_HCTRL5 0x35
(...)
> +struct isa1200_config {
(...)
> + u32 duty;
> +};
> + /* Duty cycle */
> + regmap_write(isa->map, ISA1200_HCTRL5, config->period >> 1);
(...)
> + if (isa->clk)
> + regmap_write(isa->map, ISA1200_HCTRL5, config->duty);
(..)
> + if (isa->clk) {
> + ret = device_property_read_u32(dev, "imagis,period-ns",
> + &config->period);
> + if (ret)
> + return dev_err_probe(dev, ret,
> + "failed to get period\n");
> +
> + config->period /= ISA1200_HCTRL6_PERIOD_SCALE;
> + config->duty = config->period >> 1;
> + }
> +
> + if (isa->pwm) {
> + struct pwm_state state;
> +
> + pwm_init_state(isa->pwm, &state);
> +
> + if (!state.period)
> + return dev_err_probe(dev, -EINVAL,
> + "PWM period cannot be zero\n");
> +
> + config->freq = div64_u64(NANO, state.period * config->clkdiv);
> + config->duty = state.period >> 1;
So you don't need the same code writing
regmap_write(isa->map, ISA1200_HCTRL5, config->period >> 1);
above, just use confg->duty which contains config->period >> 1
(...)
> + device_property_read_u32(dev, "imagis,duty-cycle-ns", &config->duty);
I'm not sure about this, it works for me when I set this to 100
resulting in a register write of 100 to ISA1200_HCTRL5. But are
we sure that this register is expressed in nanoseconds? I think
some calculation is needed here (and probably another value
in my device tree).
Yours,
Linus Walleij
next prev parent reply other threads:[~2026-04-30 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 11:43 [PATCH v2 0/2] input: misc: add support for Imagis ISA1200 haptic motor driver Svyatoslav Ryhel
2026-04-28 11:43 ` [PATCH v2 1/2] dt-bindings: input: Document " Svyatoslav Ryhel
2026-04-28 11:43 ` [PATCH v2 2/2] Input: isa1200 - new driver for Imagis ISA1200 Svyatoslav Ryhel
2026-04-30 9:22 ` Linus Walleij [this message]
2026-04-30 9:46 ` Svyatoslav Ryhel
2026-05-05 10:39 ` Linus Walleij
2026-05-05 11:42 ` Svyatoslav Ryhel
2026-04-30 9:16 ` [PATCH v2 0/2] input: misc: add support for Imagis ISA1200 haptic motor driver Linus Walleij
2026-04-30 9:52 ` Svyatoslav Ryhel
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=CAD++jLkU-G38xtzzfAV_otiYuM2G5NHdCdtjFjsy2AjpG22_rg@mail.gmail.com \
--to=linusw@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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