From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>, Sekhar Nori <nsekhar@ti.com>,
Kevin Hilman <khilman@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v3 2/6] usb: ohci-da8xx: let the regulator framework keep track of use count
Date: Tue, 9 Apr 2019 13:36:12 +0300 [thread overview]
Message-ID: <7c968006-0cdc-d4cf-622f-9cda52490aa1@cogentembedded.com> (raw)
In-Reply-To: <20190409082855.15373-3-brgl@bgdev.pl>
On 04/09/2019 11:28 AM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> There's no reason to have a separate variable to keep track of the
> regulator state. The regulator core already does that. Remove
> reg_enabled from struct da8xx_ohci_hcd.
>
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
> ---
> drivers/usb/host/ohci-da8xx.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/usb/host/ohci-da8xx.c b/drivers/usb/host/ohci-da8xx.c
> index ca8a94f15ac0..9c6d1f03b871 100644
> --- a/drivers/usb/host/ohci-da8xx.c
> +++ b/drivers/usb/host/ohci-da8xx.c
[...]
> @@ -100,21 +99,18 @@ static int ohci_da8xx_set_power(struct usb_hcd *hcd, int on)
> if (!da8xx_ohci->vbus_reg)
> return 0;
>
> - if (on && !da8xx_ohci->reg_enabled) {
> + if (on) {
> ret = regulator_enable(da8xx_ohci->vbus_reg);
> if (ret) {
> dev_err(dev, "Failed to enable regulator: %d\n", ret);
> return ret;
> }
> - da8xx_ohci->reg_enabled = 1;
> -
> - } else if (!on && da8xx_ohci->reg_enabled) {
> + } else if (!on) {
This can be reduced to simple *else* now.
> ret = regulator_disable(da8xx_ohci->vbus_reg);
> if (ret) {
> dev_err(dev, "Failed to disable regulator: %d\n", ret);
> return ret;
> }
> - da8xx_ohci->reg_enabled = 0;
> }
>
> return 0;
MBR, Sergei
next prev parent reply other threads:[~2019-04-09 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 8:28 [PATCH v3 0/6] ARM: davinci: ohci-da8xx: model the vbus GPIO as a fixed regulator Bartosz Golaszewski
2019-04-09 8:28 ` [PATCH v3 1/6] ARM: davinci: add missing sentinels to GPIO lookup tables Bartosz Golaszewski
2019-04-09 8:28 ` [PATCH v3 2/6] usb: ohci-da8xx: let the regulator framework keep track of use count Bartosz Golaszewski
2019-04-09 10:36 ` Sergei Shtylyov [this message]
2019-04-09 8:28 ` [PATCH v3 3/6] usb: ohci-da8xx: disable the regulator if the overcurrent irq fired Bartosz Golaszewski
2019-04-09 17:17 ` Alan Stern
2019-04-09 8:28 ` [PATCH v3 4/6] ARM: davinci: omapl138-hawk: add a fixed regulator for ohci-da8xx Bartosz Golaszewski
2019-04-09 8:28 ` [PATCH v3 5/6] ARM: davinci: da830-evm: " Bartosz Golaszewski
2019-04-09 8:28 ` [PATCH v3 6/6] usb: ohci-da8xx: drop the vbus GPIO Bartosz Golaszewski
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=7c968006-0cdc-d4cf-622f-9cda52490aa1@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=stern@rowland.harvard.edu \
/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®