From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Liu Shixin" <liushixin2@huawei.com>,
linux-usb@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>,
"Chuhong Yuan" <hslester96@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH fix] Revert "USB: bcma: Add a check for devm_gpiod_get"
Date: Fri, 1 Oct 2021 10:59:31 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2110011054560.233543@ramsan.of.borg> (raw)
In-Reply-To: <20210831065419.18371-1-zajec5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]
Hi Rafał,
On Tue, 31 Aug 2021, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> This reverts commit f3de5d857bb2362b00e2a8d4bc886cd49dcb66db.
>
> That commit broke USB on all routers that have USB always powered on and
> don't require toggling any GPIO. It's a majority of devices actually.
>
> The original code worked and seemed safe: vcc GPIO is optional and
> bcma_hci_platform_power_gpio() takes care of checking the pointer before
> using it.
>
> This revert fixes:
> [ 10.801127] bcma_hcd: probe of bcma0:11 failed with error -2
>
> Cc: Chuhong Yuan <hslester96@gmail.com>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Thanks for your patch, which is being backported to stable.
> --- a/drivers/usb/host/bcma-hcd.c
> +++ b/drivers/usb/host/bcma-hcd.c
> @@ -406,12 +406,9 @@ static int bcma_hcd_probe(struct bcma_device *core)
> return -ENOMEM;
> usb_dev->core = core;
>
> - if (core->dev.of_node) {
> + if (core->dev.of_node)
> usb_dev->gpio_desc = devm_gpiod_get(&core->dev, "vcc",
> GPIOD_OUT_HIGH);
> - if (IS_ERR(usb_dev->gpio_desc))
> - return PTR_ERR(usb_dev->gpio_desc);
> - }
This means real errors and probe deferral are no longer handled.
What about using devm_gpiod_get_optional() instead?
After that, the check in bcma_hci_platform_power_gpio() can be removed,
as gpiod_set_value() handles NULL pointers fine.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
parent reply other threads:[~2021-10-01 8:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210831065419.18371-1-zajec5@gmail.com>]
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=alpine.DEB.2.22.394.2110011054560.233543@ramsan.of.borg \
--to=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hslester96@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=rafal@milecki.pl \
--cc=zajec5@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
all inboxes | Powered by JetHome®