From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
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 v7 8/8] pwm: pca9685: Add error messages for failed regmap calls
Date: Wed, 7 Apr 2021 22:47:45 +0200 [thread overview]
Message-ID: <YG4acW/xZS2+/kDz@workstation.tuxnet> (raw)
In-Reply-To: <20210407061619.fl6ffos6csvgtnjh@pengutronix.de>
On Wed, Apr 07, 2021 at 08:16:19AM +0200, Uwe Kleine-König wrote:
> On Tue, Apr 06, 2021 at 06:41:40PM +0200, Clemens Gruber wrote:
> > Regmap operations can fail if the underlying subsystem is not working
> > properly (e.g. hogged I2C bus, etc.)
> > As this is useful information for the user, print an error message if it
> > happens.
> > Let probe fail if the first regmap_read or the first regmap_write fails.
> >
> > Signed-off-by: Clemens Gruber <clemens.gruber@pqgruber.com>
> > ---
> > Changes since v6:
> > - Rebased
> >
> > drivers/pwm/pwm-pca9685.c | 83 ++++++++++++++++++++++++++++-----------
> > 1 file changed, 59 insertions(+), 24 deletions(-)
> >
> > diff --git a/drivers/pwm/pwm-pca9685.c b/drivers/pwm/pwm-pca9685.c
> > index cf0c98e4ef44..8a4993882b40 100644
> > --- a/drivers/pwm/pwm-pca9685.c
> > +++ b/drivers/pwm/pwm-pca9685.c
> > @@ -107,6 +107,30 @@ static bool pca9685_prescaler_can_change(struct pca9685 *pca, int channel)
> > return test_bit(channel, pca->pwms_enabled);
> > }
> >
> > +static int pca9685_read_reg(struct pca9685 *pca, unsigned int reg, unsigned int *val)
> > +{
> > + struct device *dev = pca->chip.dev;
> > + int err;
> > +
> > + err = regmap_read(pca->regmap, reg, val);
> > + if (err != 0)
> > + dev_err(dev, "regmap_read of register 0x%x failed: %d\n", reg, err);
>
> Please use %pe to emit the error code instead of %d.
Will do.
>
> > +
> > + return err;
> > +}
> > +
> > +static int pca9685_write_reg(struct pca9685 *pca, unsigned int reg, unsigned int val)
> > +{
> > + struct device *dev = pca->chip.dev;
> > + int err;
> > +
> > + err = regmap_write(pca->regmap, reg, val);
> > + if (err != 0)
> > + dev_err(dev, "regmap_write to register 0x%x failed: %d\n", reg, err);
> > +
> > + return err;
> > +}
> > +
> > /* Helper function to set the duty cycle ratio to duty/4096 (e.g. duty=2048 -> 50%) */
> > static void pca9685_pwm_set_duty(struct pca9685 *pca, int channel, unsigned int duty)
> > {
> > @@ -115,12 +139,12 @@ static void pca9685_pwm_set_duty(struct pca9685 *pca, int channel, unsigned int
> >
> > if (duty == 0) {
> > /* Set the full OFF bit, which has the highest precedence */
> > - regmap_write(pca->regmap, REG_OFF_H(channel), LED_FULL);
> > + pca9685_write_reg(pca, REG_OFF_H(channel), LED_FULL);
>
> You didn't check all return codes? How did you select the calls to
> check?
No, because it would become a big mess and really obstruct readability
in my opinion.
So I chose some kind of middleground:
I decided to check the first regmap_read and regmap_write in probe and
return the error code if something goes wrong there.
If something goes wrong after probe, I only print an error message.
Is that acceptable?
Thanks,
Clemens
next prev parent reply other threads:[~2021-04-07 20:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 16:41 [PATCH v7 1/8] pwm: pca9685: Switch to atomic API Clemens Gruber
2021-04-06 16:41 ` [PATCH v7 2/8] pwm: pca9685: Support hardware readout Clemens Gruber
2021-04-07 5:31 ` Uwe Kleine-König
2021-04-07 7:33 ` Clemens Gruber
2021-04-07 9:09 ` Uwe Kleine-König
2021-04-07 9:53 ` Clemens Gruber
2021-04-06 16:41 ` [PATCH v7 3/8] pwm: pca9685: Improve runtime PM behavior Clemens Gruber
2021-04-09 13:03 ` Thierry Reding
2021-04-09 16:08 ` Clemens Gruber
2021-04-06 16:41 ` [PATCH v7 4/8] dt-bindings: pwm: Support new PWM_STAGGERING_ALLOWED flag Clemens Gruber
2021-04-07 5:33 ` Uwe Kleine-König
2021-04-09 12:27 ` Thierry Reding
2021-04-10 14:01 ` Uwe Kleine-König
2021-04-10 14:02 ` Uwe Kleine-König
2021-04-06 16:41 ` [PATCH v7 5/8] pwm: core: " Clemens Gruber
2021-04-07 5:46 ` Uwe Kleine-König
2021-04-07 20:21 ` Clemens Gruber
2021-04-07 21:34 ` Uwe Kleine-König
2021-04-08 12:50 ` Thierry Reding
2021-04-08 15:51 ` Clemens Gruber
2021-04-08 17:36 ` Uwe Kleine-König
2021-04-08 18:14 ` Clemens Gruber
2021-04-09 11:25 ` Thierry Reding
2021-04-09 16:02 ` Clemens Gruber
2021-04-09 21:35 ` Uwe Kleine-König
2021-04-09 11:10 ` Thierry Reding
2021-04-06 16:41 ` [PATCH v7 6/8] pwm: pca9685: " Clemens Gruber
2021-04-06 16:41 ` [PATCH v7 7/8] pwm: pca9685: Restrict period change for enabled PWMs Clemens Gruber
2021-04-07 6:12 ` Uwe Kleine-König
2021-04-07 20:41 ` Clemens Gruber
2021-04-07 21:38 ` Uwe Kleine-König
2021-04-06 16:41 ` [PATCH v7 8/8] pwm: pca9685: Add error messages for failed regmap calls Clemens Gruber
2021-04-07 6:16 ` Uwe Kleine-König
2021-04-07 20:47 ` Clemens Gruber [this message]
2021-04-07 21:41 ` Uwe Kleine-König
2021-04-07 5:24 ` [PATCH v7 1/8] pwm: pca9685: Switch to atomic API Uwe Kleine-König
2021-04-07 7:26 ` 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=YG4acW/xZS2+/kDz@workstation.tuxnet \
--to=clemens.gruber@pqgruber.com \
--cc=TheSven73@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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