From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Yang Yingliang <yangyingliang@huawei.com>, linux-input@vger.kernel.org
Cc: dmitry.torokhov@gmail.com
Subject: Re: [PATCH -next 4/4] Input: gpio_keys_polled - Switch to use dev_err_probe() helper
Date: Thu, 22 Sep 2022 10:52:11 +0200 [thread overview]
Message-ID: <87sfkjg5ac.fsf@baylibre.com> (raw)
In-Reply-To: <87y1ubg5g4.fsf@baylibre.com>
On Thu, Sep 22, 2022 at 10:48, Mattijs Korpershoek <mkorpershoek@baylibre.com> wrote:
> Hi Yang,
>
> Thank you for your patch,
>
> On Tue, Sep 20, 2022 at 23:30, 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/keyboard/gpio_keys_polled.c | 8 ++------
>> 1 file changed, 2 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/input/keyboard/gpio_keys_polled.c b/drivers/input/keyboard/gpio_keys_polled.c
>> index c3937d2fc744..ba00ecfbd343 100644
>> --- a/drivers/input/keyboard/gpio_keys_polled.c
>> +++ b/drivers/input/keyboard/gpio_keys_polled.c
>> @@ -299,13 +299,9 @@ static int gpio_keys_polled_probe(struct platform_device *pdev)
>> NULL, GPIOD_IN,
>> button->desc);
>> if (IS_ERR(bdata->gpiod)) {
>> - error = PTR_ERR(bdata->gpiod);
>> - if (error != -EPROBE_DEFER)
>> - dev_err(dev,
>> - "failed to get gpio: %d\n",
>> - error);
>> fwnode_handle_put(child);
>> - return error;
>> + return dev_err_probe(dev, PTR_ERR(bdata->gpiod),
>> + "failed to get gpio\n");
>
> 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
Argh, I missed the link. here it is:
[1] https://lore.kernel.org/r/YWTpg35wyYS1uoFZ@google.com
>
>> }
>> } else if (gpio_is_valid(button->gpio)) {
>> /*
>> --
>> 2.25.1
next prev parent reply other threads:[~2022-09-22 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 15:30 [PATCH -next 1/4] Input: adc-joystick - Switch to use dev_err_probe() helper Yang Yingliang
2022-09-20 15:30 ` [PATCH -next 2/4] Input: bcm-keypad " Yang Yingliang
2022-09-22 8:47 ` Mattijs Korpershoek
2022-09-20 15:30 ` [PATCH -next 3/4] Input: gpio_keys " Yang Yingliang
2022-09-22 8:48 ` Mattijs Korpershoek
2022-09-22 8:52 ` Mattijs Korpershoek
2022-09-20 15:30 ` [PATCH -next 4/4] Input: gpio_keys_polled " Yang Yingliang
2022-09-22 8:48 ` Mattijs Korpershoek
2022-09-22 8:52 ` Mattijs Korpershoek [this message]
2022-09-22 8:46 ` [PATCH -next 1/4] Input: adc-joystick " Mattijs Korpershoek
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=87sfkjg5ac.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox