From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Yang Yingliang <yangyingliang@huawei.com>, linux-input@vger.kernel.org
Cc: dmitry.torokhov@gmail.com, thierry.reding@gmail.com,
u.kleine-koenig@pengutronix.de, yangyingliang@huawei.com
Subject: Re: [PATCH -next 1/5] Input: da7280 - Switch to use dev_err_probe() helper
Date: Thu, 22 Sep 2022 10:51:25 +0200 [thread overview]
Message-ID: <87v8pfg5bm.fsf@baylibre.com> (raw)
In-Reply-To: <20220920153656.3486879-1-yangyingliang@huawei.com>
Hi Yang,
Thank you for your series,
On Tue, Sep 20, 2022 at 23:36, Yang Yingliang <yangyingliang@huawei.com> wrote:
> In the probe path, dev_err() can be replaced with dev_err_probe()
> which will check if error code is -EPROBE_DEFER and prints the
> error name. It also sets the defer probe reason which can be
> checked later through debugfs.
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
> drivers/input/misc/da7280.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/input/misc/da7280.c b/drivers/input/misc/da7280.c
> index b08610d6e575..b1ca4fd94e9e 100644
> --- a/drivers/input/misc/da7280.c
> +++ b/drivers/input/misc/da7280.c
> @@ -1166,12 +1166,9 @@ static int da7280_probe(struct i2c_client *client,
> if (haptics->const_op_mode == DA7280_PWM_MODE) {
> haptics->pwm_dev = devm_pwm_get(dev, NULL);
> error = PTR_ERR_OR_ZERO(haptics->pwm_dev);
> - if (error) {
> - if (error != -EPROBE_DEFER)
> - dev_err(dev, "Unable to request PWM: %d\n",
> - error);
> - return error;
> - }
> + if (error)
> + return dev_err_probe(dev, error,
> + "Unable to request PWM\n");
For the whole series:
If we look at the input tree, we can see that there is no occurence of
dev_err_probe():
$ ~/src/linux/drivers/input/ 483fed3b5dc8 grep -rsn dev_err_probe
$ ~/src/linux/drivers/input/ 483fed3b5dc8
The reason for this is that the input maintainer (Dmitry) dislikes
dev_err_probe() as he stated in [1]
So I don't think he will apply this.
Regards,
Mattijs
[1] https://lore.kernel.org/r/YWTpg35wyYS1uoFZ@google.com
>
> /* Sync up PWM state and ensure it is off. */
> pwm_init_state(haptics->pwm_dev, &state);
> --
> 2.25.1
next prev parent reply other threads:[~2022-09-22 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 15:36 [PATCH -next 1/5] Input: da7280 - Switch to use dev_err_probe() helper Yang Yingliang
2022-09-20 15:36 ` [PATCH -next 2/5] Input: gpio-vibra " Yang Yingliang
2022-09-20 15:36 ` [PATCH -next 3/5] Input: pwm-beeper " Yang Yingliang
2022-09-20 15:36 ` [PATCH -next 4/5] Input: pwm-vibra " Yang Yingliang
2022-09-20 15:36 ` [PATCH -next 5/5] Input: rotary_encoder " Yang Yingliang
2022-09-22 8:51 ` Mattijs Korpershoek [this message]
2022-09-22 10:23 ` [PATCH -next 1/5] Input: da7280 " Yang Yingliang
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=87v8pfg5bm.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yangyingliang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.