From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 1/3] ARM: davinci: da830: Handle vbus with a regulator
Date: Tue, 22 Nov 2016 16:05:16 +0530 [thread overview]
Message-ID: <fad5d7af-3f54-020e-c037-0a46bc88c39d@ti.com> (raw)
In-Reply-To: <20161121165349.29128-2-ahaslam@baylibre.com>
On Monday 21 November 2016 10:23 PM, Axel Haslam wrote:
> static __init void da830_evm_usb_init(void)
> {
> @@ -145,23 +123,13 @@ static __init void da830_evm_usb_init(void)
> return;
> }
>
> - ret = gpio_request(ON_BD_USB_DRV, "ON_BD_USB_DRV");
> - if (ret) {
> - pr_err("%s: failed to request GPIO for USB 1.1 port power control: %d\n",
> - __func__, ret);
> - return;
> - }
> - gpio_direction_output(ON_BD_USB_DRV, 0);
> + gpiod_add_lookup_table(&usb11_gpios_table);
>
> - ret = gpio_request(ON_BD_USB_OVC, "ON_BD_USB_OVC");
> - if (ret) {
> - pr_err("%s: failed to request GPIO for USB 1.1 port over-current indicator: %d\n",
> - __func__, ret);
> - return;
> - }
> - gpio_direction_input(ON_BD_USB_OVC);
> + ret = platform_device_register(&da8xx_usb11_regulator);
> + if (ret)
> + pr_warn("fail to add ohci regulator\n");
Can you follow the same style as used in other error/warning messages in
this function (adding a function name prefix, printing of error code).
Thanks,
Sekhar
next prev parent reply other threads:[~2016-11-22 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 16:53 [RESEND PATCH 0/3] ARM: davinci: OHCI: Use a regulator instead of callbacks Axel Haslam
2016-11-21 16:53 ` [RESEND PATCH 1/3] ARM: davinci: da830: Handle vbus with a regulator Axel Haslam
2016-11-22 10:35 ` Sekhar Nori [this message]
2016-11-21 16:53 ` [RESEND PATCH 2/3] ARM: davinci: hawk: Remove vbus and over current gpios Axel Haslam
2016-11-22 10:37 ` Sekhar Nori
2016-11-22 15:41 ` Axel Haslam
2016-11-23 5:12 ` Sekhar Nori
2016-11-21 16:53 ` [RESEND PATCH 3/3] ARM: davinci: remove ohci platform usage Axel Haslam
2016-11-22 10:42 ` Sekhar Nori
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=fad5d7af-3f54-020e-c037-0a46bc88c39d@ti.com \
--to=nsekhar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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