From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Clemens Gruber <clemens.gruber@pqgruber.com>
Cc: linux-pwm@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
Sven Van Asbroeck <TheSven73@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 6/8] pwm: pca9685: Support new PWM_USAGE_POWER flag
Date: Tue, 13 Apr 2021 12:34:12 +0200 [thread overview]
Message-ID: <20210413103412.ngvtk5cw2ftyjvob@pengutronix.de> (raw)
In-Reply-To: <YHR/Xm5nOjrSwVYs@workstation.tuxnet>
[-- Attachment #1: Type: text/plain, Size: 3620 bytes --]
Hi Clemens,
On Mon, Apr 12, 2021 at 07:11:58PM +0200, Clemens Gruber wrote:
> On Mon, Apr 12, 2021 at 06:30:45PM +0200, Uwe Kleine-König wrote:
> > On Mon, Apr 12, 2021 at 03:27:43PM +0200, Clemens Gruber wrote:
> > > static unsigned int pca9685_pwm_get_duty(struct pca9685 *pca, int channel)
> > > {
> > > - unsigned int off_h = 0, val = 0;
> > > + struct pwm_device *pwm = &pca->chip.pwms[channel];
> > > + unsigned int off = 0, on = 0, val = 0;
> > >
> > > if (WARN_ON(channel >= PCA9685_MAXCHAN)) {
> > > /* HW does not support reading state of "all LEDs" channel */
> > > return 0;
> > > }
> > >
> > > - regmap_read(pca->regmap, LED_N_OFF_H(channel), &off_h);
> > > - if (off_h & LED_FULL) {
> > > + regmap_read(pca->regmap, LED_N_OFF_H(channel), &off);
> > > + if (off & LED_FULL) {
> > > /* Full OFF bit is set */
> > > return 0;
> > > }
> > >
> > > - regmap_read(pca->regmap, LED_N_ON_H(channel), &val);
> > > - if (val & LED_FULL) {
> > > + regmap_read(pca->regmap, LED_N_ON_H(channel), &on);
> > > + if (on & LED_FULL) {
> > > /* Full ON bit is set */
> > > return PCA9685_COUNTER_RANGE;
> > > }
> > >
> > > - val = 0;
> > > regmap_read(pca->regmap, LED_N_OFF_L(channel), &val);
> > > - return ((off_h & 0xf) << 8) | (val & 0xff);
> > > + off = ((off & 0xf) << 8) | (val & 0xff);
> > > + if (!pwm->args.usage_power)
> > > + return off;
> > > +
> > > + /* Read ON register to calculate duty cycle of staggered output */
> > > + val = 0;
> > > + regmap_read(pca->regmap, LED_N_ON_L(channel), &val);
> > > + on = ((on & 0xf) << 8) | (val & 0xff);
> > > + return (off - on) & (PCA9685_COUNTER_RANGE - 1);
> >
> > If LED_N_ON is != 0 but usage_power is false, the returned state is
> > bogus.
>
> If usage_power is false, LED_N_ON is guaranteed to be 0. It is reset to
> 0 in probe and never changed. Or did I miss something?
Ah right, so my concern is only a challenge once the reset in probe goes
away.
> > > }
> > >
> > > #if IS_ENABLED(CONFIG_GPIOLIB)
> > > @@ -439,9 +469,11 @@ static int pca9685_pwm_probe(struct i2c_client *client,
> > > reg &= ~(MODE1_ALLCALL | MODE1_SUB1 | MODE1_SUB2 | MODE1_SUB3);
> > > regmap_write(pca->regmap, PCA9685_MODE1, reg);
> > >
> > > - /* Reset OFF registers to POR default */
> > > + /* Reset OFF/ON registers to POR default */
> > > regmap_write(pca->regmap, PCA9685_ALL_LED_OFF_L, LED_FULL);
> > > regmap_write(pca->regmap, PCA9685_ALL_LED_OFF_H, LED_FULL);
> > > + regmap_write(pca->regmap, PCA9685_ALL_LED_ON_L, 0);
> > > + regmap_write(pca->regmap, PCA9685_ALL_LED_ON_H, 0);
> > >
> > > pca->chip.ops = &pca9685_pwm_ops;
> > > /* Add an extra channel for ALL_LED */
> > > @@ -450,6 +482,9 @@ static int pca9685_pwm_probe(struct i2c_client *client,
> > > pca->chip.dev = &client->dev;
> > > pca->chip.base = -1;
> > >
> > > + pca->chip.of_xlate = of_pwm_xlate_with_flags;
> > > + pca->chip.of_pwm_n_cells = 3;
> > > +
> >
> > Huh, you're incompatibly changing the device tree binding here.
>
> No, I don't think so:
>
> The third cell is optional with of_pwm_xlate_with_flags.
> So previous DTs with pwm-cells = <2> will still work.
I thought that .of_pwm_n_cells was enforced, let me check the code ... I
had in mind that of_pwm_get() enforced that, but I cannot find it, so I
guess you're right and my concern is unjustified.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-04-13 10:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 13:27 [PATCH v8 1/8] pwm: pca9685: Switch to atomic API Clemens Gruber
2021-04-12 13:27 ` [PATCH v8 2/8] pwm: pca9685: Support hardware readout Clemens Gruber
2021-04-12 16:21 ` Uwe Kleine-König
2021-04-12 13:27 ` [PATCH v8 3/8] pwm: pca9685: Improve runtime PM behavior Clemens Gruber
2021-04-12 13:27 ` [PATCH v8 4/8] dt-bindings: pwm: Support new PWM_USAGE_POWER flag Clemens Gruber
2021-04-12 16:27 ` Uwe Kleine-König
2021-04-12 16:46 ` Clemens Gruber
2021-04-13 11:38 ` Uwe Kleine-König
2021-04-13 11:41 ` Thierry Reding
2021-04-13 11:51 ` Thierry Reding
2021-04-13 17:56 ` Uwe Kleine-König
2021-04-15 16:27 ` Thierry Reding
2021-04-16 9:32 ` Uwe Kleine-König
2021-04-16 10:45 ` Thierry Reding
2021-04-18 13:30 ` Uwe Kleine-König
2021-04-16 13:55 ` Thierry Reding
2021-04-16 15:39 ` Rob Herring
2021-04-16 15:54 ` Clemens Gruber
2021-04-17 15:44 ` Uwe Kleine-König
2021-04-12 13:27 ` [PATCH v8 5/8] pwm: core: " Clemens Gruber
2021-04-12 13:27 ` [PATCH v8 6/8] pwm: pca9685: " Clemens Gruber
2021-04-12 16:30 ` Uwe Kleine-König
2021-04-12 17:11 ` Clemens Gruber
2021-04-13 10:34 ` Uwe Kleine-König [this message]
2021-04-12 13:27 ` [PATCH v8 7/8] pwm: pca9685: Restrict period change for enabled PWMs Clemens Gruber
2021-04-17 15:46 ` Uwe Kleine-König
2021-04-12 13:27 ` [PATCH v8 8/8] pwm: pca9685: Add error messages for failed regmap calls Clemens Gruber
2021-04-17 15:47 ` Uwe Kleine-König
2021-04-12 16:18 ` [PATCH v8 1/8] pwm: pca9685: Switch to atomic API Uwe Kleine-König
2021-04-12 16:39 ` Clemens Gruber
2021-04-12 20:10 ` Uwe Kleine-König
2021-04-13 12:11 ` Clemens Gruber
2021-04-13 12:17 ` Clemens Gruber
2021-04-13 12:37 ` Thierry Reding
2021-04-13 13:06 ` Clemens Gruber
2021-04-13 19:38 ` Uwe Kleine-König
2021-04-14 12:09 ` Clemens Gruber
2021-04-14 19:21 ` Uwe Kleine-König
2021-04-14 19:45 ` Clemens Gruber
2021-04-15 6:48 ` Uwe Kleine-König
2021-04-17 15:37 ` Uwe Kleine-König
2021-04-17 16:40 ` Clemens Gruber
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=20210413103412.ngvtk5cw2ftyjvob@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=TheSven73@gmail.com \
--cc=clemens.gruber@pqgruber.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).