From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: DT && i.MX USB
Date: Tue, 29 Oct 2013 10:23:33 +0100 [thread overview]
Message-ID: <20131029092333.GS30088@pengutronix.de> (raw)
In-Reply-To: <1383037497.37165744@f327.i.mail.ru>
On Tue, Oct 29, 2013 at 01:04:57PM +0400, Alexander Shiyan wrote:
> > On Mon, Oct 28, 2013 at 07:50:21PM +0400, Alexander Shiyan wrote:
> > > Hello.
> > >
> > > I am trying to migrate i.MX51 ConnectCore board for use DT.
> > > Most stuff are done but I cannot understand how USB subsystem
> > > works with devicetree.
> > >
> > > First, why barebox uses own "barebox,dr_mode" and "barebox,phy_type"
> > > properties instead of use kernel "dr_mode" and "phy_type"?
> >
> > By the time I created this binding the binding for the kernel was not
> > mainline, so I decided to use barebox,x to not end up with an
> > incompatible binding. As the binding made it mainline now we can drop
> > the "barebox," now.
>
> Understood.
>
> > > Second, how specify flags for USB ports, for example MXC_EHCI_INTERNAL_PHY?
> > > In DT case we can not do it and as result desired port not functional...
> >
> > Could it be that this flag should simply be dropped? According to the
> > Block diagram (Freescale i.MX53 ref manual v2.1, page 4700) the otg port
> > is hardwired to the internal utmi phy, so having this configurable makes
> > no sense.
>
> I checked it for i.MX51. Everything works.
> Will it be the right solution for all i.MX CPUs?
At least for i.MX51/53 this is correct. For i.MX51 it seems to be
possible to use the internal UTMI phy or an external ULPI phy for the
OTG port.
> If so, I will write a patch for both issues. Or you?
Go ahead and write a patch. I'll give it a test on my i.MX51 efikasb
then.
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-10-29 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 15:50 Alexander Shiyan
2013-10-29 8:08 ` Sascha Hauer
2013-10-29 9:04 ` Alexander Shiyan
2013-10-29 9:23 ` 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=20131029092333.GS30088@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=shc_work@mail.ru \
/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