From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: usb support for imx35 ?
Date: Tue, 20 Oct 2009 10:21:08 +0200 [thread overview]
Message-ID: <20091020082108.GP8818@pengutronix.de> (raw)
In-Reply-To: <200910201155.54578.a.babich@rez.ru>
On Tue, Oct 20, 2009 at 11:55:54AM +0600, Alexei Babich wrote:
> Hello all.
>
> Tell me please, what is the status of support for USB-HOST in the microcontroller Freescale imx35?
> Thank you.
Basically the same status as for i.MX27/31/25. There have been patches
to add USB host support from Daniel Mack. Hopefully they go in in the
next merge window.
All mentioned i.MXs have the same otg core with some minor differences.
Daniels patches aim for i.MX31, but once these are mainline, the rest is
easy.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2009-10-20 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 5:55 usb support for imx35 ? Alexei Babich
2009-10-20 8:21 ` Sascha Hauer [this message]
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=20091020082108.GP8818@pengutronix.de \
--to=s.hauer@pengutronix.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).