From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] at91/USB: at91sam9g45 series USB host integration
Date: Wed, 16 Sep 2009 18:17:01 +0200 [thread overview]
Message-ID: <4AB10F7D.9060706@atmel.com> (raw)
In-Reply-To: <200906190226.56278.david-b@pacbell.net>
Hi,
I come back on this topic as at91sam9g45 is now in mainline. I need this
integration code to have the USB EHCI work on the evaluation kit.
David Brownell :
> On Friday 19 June 2009, Haavard Skinnemoen wrote:
>> David Brownell wrote:
>>>> --- a/arch/arm/mach-at91/at91sam9g45_devices.c
>>>> +++ b/arch/arm/mach-at91/at91sam9g45_devices.c
>>>> + /* Enable VBus control for UHP ports */
>>>> + for (i = 0; i < data->ports; i++) {
>>>> + if (data->vbus_pin[i])
>>>> + at91_set_gpio_output(data->vbus_pin[i], 0);
>>> This should gpio_request() and gpio_direction_output().
>> Hmm...I thought the driver was supposed to call gpio_request(), not the
>> platform code?
>
> In some cases. This isn't a good case for that. Especially
> if it's going to call gpio_direction_output() ... which needs
> gpio_request() to have been done first.
Ok, I am building a patch on top of this one that uses these calls. This
way I can change both vbus pin configuration: OCHI and EHCI.
Best regards,
--
Nicolas Ferre
next parent reply other threads:[~2009-09-16 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1244547493-19654-1-git-send-email-nicolas.ferre@atmel.com>
[not found] ` <200906190043.00428.david-b@pacbell.net>
[not found] ` <20090619095148.67a74ed9@hskinnemoen-d830>
[not found] ` <200906190226.56278.david-b@pacbell.net>
2009-09-16 16:17 ` Nicolas Ferre [this message]
2009-09-16 17:29 ` [PATCH] at91: use gpiolib calls for USB vbus pin on at91sam9g45 Nicolas Ferre
2009-09-16 21:53 ` Jean-Christophe PLAGNIOL-VILLARD
2009-09-17 8:13 ` Nicolas Ferre
2009-09-17 9:00 ` Jean-Christophe PLAGNIOL-VILLARD
2009-09-18 8:40 ` Nicolas Ferre
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=4AB10F7D.9060706@atmel.com \
--to=nicolas.ferre@atmel.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;
as well as URLs for NNTP newsgroup(s).