From: Felipe Balbi <balbi@ti.com>
To: Subbaraya Sundeep Bhatta <subbaraya.sundeep.bhatta@xilinx.com>
Cc: Peter Chen <peter.chen@freescale.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>,
Punnaiah Choudary Kalluri <punnaia@xilinx.com>
Subject: Re: Chipidea ULPI driver
Date: Thu, 10 Sep 2015 09:43:49 -0500 [thread overview]
Message-ID: <20150910144349.GH8982@saruman.tx.rr.com> (raw)
In-Reply-To: <F1B223389110CE49B4CF055ABA2E5D3D78C7EB88@XAP-PVEXMBX02.xlnx.xilinx.com>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
(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
> 2. Write ci_hdrc_zynq.c which does PHY access required for Zynq.
not this
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2015-09-10 14:43 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 ` Felipe Balbi [this message]
2015-09-10 14:57 ` Chipidea ULPI driver 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
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=20150910144349.GH8982@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.