DT && i.MX USB

DT && i.MX USB

[Alexander Shiyan]

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"?

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...

Thanks.

---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: DT && i.MX USB

[Sascha Hauer]

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.

> 
> 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.

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

Re: DT && i.MX USB

[Alexander Shiyan]

> 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?
If so, I will write a patch for both issues. Or you?
Thanks.

---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: DT && i.MX USB

[Sascha Hauer]

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