From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Chipidea usb otg support for IMX/MXS (device functionality)
Date: Thu, 27 Jun 2013 15:49:00 +0200 [thread overview]
Message-ID: <201306271549.01136.marex@denx.de> (raw)
In-Reply-To: <F281D0F91ED19E4D8E63A7504E8A649803EFBC6C@039-SN2MPN1-023.039d.mgd.msft.net>
Hi Peter,
> > No, I don't have this one available right now. I tried both MX23
> > Olinuxino maxi
> > (I just mutilated the board so that I cut traces to the USB devices on
> > the board
> > and routed out USB gadget connector) and a custom MX23 board.
> >
> > Note that both have working USB peripheral mode in U-Boot too, but the
> > driver in
> > U-Boot is very minimalistic.
>
> You mean, the larger data transfer with USB peripheral mode is ok at
> u-boot? but it can't work at Linux Kernel?
I stumbled across one more problem with the patches:
- I use OTG on MX28
- I configured the USB ID pin
- I set the dr_mode to "otg"
(so far so good)
- I use the port in HOST mode by plugging in a USB pendrive over the OTG-capable
reduction ; this works OK
- I disconnect the reduction and connect it to the computer ; here I get
"timeout waiting for 00000800 in 11".
This means the BSV bit in OTGSC register wasn't unset.
Interestingly enough, transition the other way around (first use in gadget mode
then in host mode) works fine, but if I do host mode -> gadget mode, I get the
timeout. Do you have any hint for me?
btw. what is the plan about cleaning up and upstreaming all these patches we
have here? Is anyone working on it? I'd hate to stomp on anyones' efforts,but
I'd also like to see this mess sorted out.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-06-27 13:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51A5A808.2070803@digi.com>
[not found] ` <F281D0F91ED19E4D8E63A7504E8A649803E8A3F3@039-SN2MPN1-021.039d.mgd.msft.net>
2013-05-29 7:50 ` Chipidea usb otg support for IMX/MXS (device functionality) maxime.ripard at free-electrons.com
2013-05-29 8:07 ` Chen Peter-B29397
2013-05-29 10:13 ` Michael Grzeschik
2013-05-29 12:19 ` maxime.ripard at free-electrons.com
2013-05-29 12:41 ` Michael Grzeschik
2013-05-30 13:53 ` maxime.ripard at free-electrons.com
2013-06-21 11:26 ` Marek Vasut
2013-06-21 12:22 ` Michael Grzeschik
2013-06-21 12:56 ` Marek Vasut
2013-06-22 2:33 ` Marek Vasut
2013-06-22 8:28 ` Chen Peter-B29397
2013-06-22 13:29 ` Marek Vasut
2013-06-24 1:37 ` Chen Peter-B29397
2013-06-24 7:08 ` Shawn Guo
2013-06-24 13:51 ` Marek Vasut
2013-06-25 1:48 ` Chen Peter-B29397
2013-06-25 18:40 ` Marek Vasut
2013-06-27 13:49 ` Marek Vasut [this message]
2013-06-28 6:48 ` Chen Peter-B29397
2013-06-28 9:42 ` Marek Vasut
2013-06-28 10:46 ` Chen Peter-B29397
2013-06-28 11:56 ` Marek Vasut
2013-06-28 13:04 ` Chen Peter-B29397
2013-06-28 13:11 ` Fabio Estevam
2013-07-01 2:06 ` Chen Peter-B29397
2013-07-07 1:10 ` Marek Vasut
2013-07-08 1:21 ` Chen Peter-B29397
2013-07-08 20:56 ` Marek Vasut
2013-07-09 1:05 ` Chen Peter-B29397
2013-07-09 10:38 ` Marek Vasut
2013-06-25 14:23 ` Fabio Estevam
2013-06-25 15:39 ` Fabio Estevam
2013-06-25 18:42 ` Marek Vasut
2013-07-09 15:07 ` Marek Vasut
2013-05-30 16:17 ` Hector Palacios
2013-06-07 9:37 ` maxime.ripard at free-electrons.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=201306271549.01136.marex@denx.de \
--to=marex@denx.de \
--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).