Messages in this thread | | | From | Punnaiah Choudary Kalluri <> | Subject | RE: Chipidea ULPI driver | Date | Thu, 10 Sep 2015 14:57:49 +0000 |
| |
> -----Original Message----- > From: Felipe Balbi [mailto:balbi@ti.com] > Sent: Thursday, September 10, 2015 8:14 PM > To: Subbaraya Sundeep Bhatta > Cc: Peter Chen; balbi@ti.com; linux-usb@vger.kernel.org; linux- > kernel@vger.kernel.org; Greg Kroah-Hartman > (gregkh@linuxfoundation.org); kishon@ti.com; Punnaiah Choudary Kalluri > Subject: Re: Chipidea ULPI driver > > (break your lines at 80-characters) > > On Thu, Sep 10, 2015 at 12:44:58PM +0000, Subbaraya Sundeep Bhatta wrote: > > Hi Peter, > > > > We are using NOP transceiver driver for USB3320 ULPI PHY with ChipIdea > > controller. > > > > Recently we found that one of the boards (zedboard) requires PHY > > register access to set VBUS. > > > > Note that our local driver we had before migrating to ChipIdea driver > > calls otg_ulpi_create with flags ULPI_OTG_DRVVBUS | > > ULPI_OTG_DRVVBUS_EXT so that VBUS is enabled at initialization. > > > > Can you please let me know how to do this with ChipIdea case? I see > > the following solutions: > > > > 1. Write ULPI driver for USB3320 similar to tusb1210. > > this
How about extending the phy-ulpi driver to use it as platform driver? So that boards that are using the ulpi compatible phy and driving vbus from the phy can use this driver.
Regards, Punnaiah > > > 2. Write ci_hdrc_zynq.c which does PHY access required for Zynq. > > not this > > -- > balbi
| |