linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Chipidea usb otg support for IMX/MXS (device functionality)
Date: Sat, 22 Jun 2013 04:33:58 +0200	[thread overview]
Message-ID: <201306220433.58281.marex@denx.de> (raw)
In-Reply-To: <201306211456.31197.marex@denx.de>

Hi,

> Dear Michael Grzeschik,
> 
> > Hi Marek,
> > 
> > On Fri, Jun 21, 2013 at 01:26:10PM +0200, Marek Vasut wrote:
> > > Hi,
> > > 
> > > > Hi,
> > > > 
> > > > On Wed, May 29, 2013 at 08:07:55AM +0000, Chen Peter-B29397 wrote:
> > > > > > Indeed, I've been using the patchset "Add tested id switch and
> > > > > > vbus connect detect support for Chipidea" from Peter for quite
> > > > > > some time on top of 3.9 and it works like a charm for the gadget
> > > > > > mode on an MX28 platform.
> > > > > > 
> > > > > > BTW, Peter, I've seen that these patches are still not merged in
> > > > > > 3.10, is there a reason for that? do you plan on sending a
> > > > > > version rebased on top of 3.10 some time in the future? I tried
> > > > > > to do the rebasing myself, but the chipidea driver seems to have
> > > > > > changed quite heavily, which makes the process quite difficult
> > > > > > when you don't know what you're doing :)
> > > > 
> > > > we already have Peter's patches on v3.10-rc3 [1].
> > > > 
> > > > > I can spend few bandwidth on upstream work recently, I may have
> > > > > more bandwidth after June 15th.
> > > > > 
> > > > > Currently, we still have no conclusion for chipidea core driver's
> > > > > coming work, like Device tree support, how to identify if the
> > > > > controller is OTG supported.
> > > > 
> > > > Yes, the next important step is getting the of propertys "dr_mode"
> > > > and "phy_type" properly used in the chipidea core.
> > > > 
> > > > [1] http://git.pengutronix.de/?p=mgr/linux.git;a=summary ->
> > > > v3.10/topic/usb-peterchen
> > > 
> > > Is anyone planning to work on this stuff and start pushing it mainline
> > > or is this effort stalled completely? What is it that's missing before
> > > these can be applied?
> > 
> > AFAIK the latest commit to that work is:
> > 
> > http://permalink.gmane.org/gmane.linux.usb.general/88121
> 
> Cool, so it seems Peter is back at it. Thanks

Peter, I dunno if you are already aware of it, but the USB peripheral mode hangs 
on MX233. It's easy to replicate for example if you try to run CDC ethernet over 
the USB peripheral mode, then telnet into the board and run "dmesg" . This will 
trigger a "larger" data transfer which will make the UDC driver hang. This 
doesn't happen on MX28 so it must be some MX233-specific thing.

Best regards,
Marek Vasut

  reply	other threads:[~2013-06-22  2:33 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 [this message]
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
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=201306220433.58281.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).