Re: am3517: fail to bring up EHCI in upstream kernel (4.9)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx> [161228 23:06]:
> On Tue, Dec 27, 2016 at 6:25 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
> > * Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx> [161220 06:37]:
> >> I'm trying to get the first USB port working on a am3517 based
> >> hardware. The system is working with 2.6.37 for now. USB tree has
> >> following structure:
> >>
> >> HSUSB1  -> TUSB1210 -> SMSC LAN9514
> >>
> >> TUSB1210's reset is connected to GPIO 57
> >> (GPMC_NCS6/SYS_NDMAREQ3/0/GPT11_PWM_EVT/GPIO_57)
> >
> > Could it be that the GPIO module reset during init turns off your
> > hub?
> >
> > You may want to set up a GPIO hog in the dts for it if you don't
> > have anything else handling that GPIO.
> 
> I've solved the problem. I've enabled EHCI PHY interface pinmux in
> u-boot and it worked at once. reset GPIO seems to be OK from the
> beginning. Have to find out why my pinmux settings in DTS didn't work.

OK good to hear you tracked it down.

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux