public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@freescale.com>
To: Subbaraya Sundeep Bhatta <subbaraya.sundeep.bhatta@xilinx.com>
Cc: Punnaiah Choudary Kalluri <punnaia@xilinx.com>,
	"balbi@ti.com" <balbi@ti.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Greg Kroah-Hartman (gregkh@linuxfoundation.org)" 
	<gregkh@linuxfoundation.org>, "kishon@ti.com" <kishon@ti.com>
Subject: Re: Chipidea ULPI driver
Date: Mon, 14 Sep 2015 13:17:26 +0800	[thread overview]
Message-ID: <20150914051725.GC19504@shlinux2> (raw)
In-Reply-To: <F1B223389110CE49B4CF055ABA2E5D3D78C813D4@XAP-PVEXMBX01.xlnx.xilinx.com>

On Fri, Sep 11, 2015 at 11:34:10AM +0000, Subbaraya Sundeep Bhatta wrote:
> Hi,
> 
> > -----Original Message-----
> > From: Peter Chen [mailto:peter.chen@freescale.com]
> > Sent: Friday, September 11, 2015 6:52 AM
> > To: Punnaiah Choudary Kalluri
> > Cc: balbi@ti.com; Subbaraya Sundeep Bhatta; linux-usb@vger.kernel.org; linux-
> > kernel@vger.kernel.org; Greg Kroah-Hartman (gregkh@linuxfoundation.org);
> > kishon@ti.com
> > Subject: Re: Chipidea ULPI driver
> > 
> > On Thu, Sep 10, 2015 at 02:57:49PM +0000, Punnaiah Choudary Kalluri wrote:
> > >
> > >
> > > > -----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.
> > >
> > 
> > Yes, you can improve phy-ulpi driver, and it can not depend on NOP transceiver
> > driver.
> 
> AFAIK phy-ulpi.c is just exporting functions and not registering to platform
> bus since it is not connected to SOC bus. I don't think we can create platform
> driver for this. I have read TUSB1210 data sheet and it is similar to USB3320
> with no additional SOC bus connection and has only ULPI interface. 
> So it should register to ULPI bus which is in kernel recently. I will make
> changes to chipidea similar to dwc3(adding ulpi.c) and write driver similar
> to tusb1210.c. Is that okay?
> 

It should be ok.

-- 

Best Regards,
Peter Chen

  reply	other threads:[~2015-09-14  6:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F1B223389110CE49B4CF055ABA2E5D3D78C7EB88@XAP-PVEXMBX02.xlnx.xilinx.com>
2015-09-10 14:43 ` Chipidea ULPI driver Felipe Balbi
2015-09-10 14:57   ` Punnaiah Choudary Kalluri
2015-09-10 15:11     ` Felipe Balbi
2015-09-11  1:22     ` Peter Chen
2015-09-11 11:34       ` Subbaraya Sundeep Bhatta
2015-09-14  5:17         ` Peter Chen [this message]
2015-09-11 16:08       ` Subbaraya Sundeep Bhatta

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=20150914051725.GC19504@shlinux2 \
    --to=peter.chen@freescale.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=punnaia@xilinx.com \
    --cc=subbaraya.sundeep.bhatta@xilinx.com \
    /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