From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@suse.cz>
Cc: David Vrabel <dvrabel@cantab.net>,
lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>,
dkrivoschokov@dev.rtsoft.ru
Subject: Re: pxa27x_udc -- support for usb gadget for pxa27x?
Date: Mon, 07 Nov 2005 10:43:52 +0000 [thread overview]
Message-ID: <1131360232.8375.50.camel@localhost.localdomain> (raw)
In-Reply-To: <436F2BB2.3040008@cantab.net>
On Mon, 2005-11-07 at 10:25 +0000, David Vrabel wrote:
> Pavel Machek wrote:
> >
> > ...for the spitz. Do you think I can just copy this one? ...eh, no,
> > will not fly, there's no SPITZ_GPIO_USB_PULLUP.
>
> There are internal pull-ups (and pull-downs) perhaps you can use those?
>
> Hmmm. Though the C5 stepping might be different -- best to check the
> "specification update".
I can confirm that you'll need to use the internal pxa27x pullups for
this. You'll probably also need to make sure GPIO 35 is low to ensure
the usb Vcc line isn't powered (as it would be in usb host mode.
Ultimately, it would be nice to have the Zaurus detect whether a usb
host or client was present (using gpio 41 maybe?) and then activate the
host (ohci) or client (pxa27x_udc) driver as appropriate.
Cheers,
Richard
next prev parent reply other threads:[~2005-11-07 10:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 22:14 pxa27x_udc -- support for usb gadget for pxa27x? Pavel Machek
2005-11-03 22:35 ` Richard Purdie
2005-11-06 19:47 ` Pavel Machek
2005-11-06 20:45 ` Pavel Machek
2005-11-07 10:25 ` David Vrabel
2005-11-07 10:43 ` Richard Purdie [this message]
2005-11-26 19:24 ` Pavel Machek
2005-11-26 19:36 ` make oldconfig issues since 2.15-rc1-mm1 Stef van der Made
2005-11-26 21:04 ` pxa27x_udc -- support for usb gadget for pxa27x? Mark Underwood
2005-11-26 21:08 ` Pavel Machek
2005-11-26 23:02 ` Mark Underwood
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=1131360232.8375.50.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=dkrivoschokov@dev.rtsoft.ru \
--cc=dvrabel@cantab.net \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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