From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 6/8] usb: chipidea: imx: add internal vbus regulator control
Date: Thu, 28 Feb 2013 14:06:09 +0800 [thread overview]
Message-ID: <20130228060608.GD19387@nchen-desktop> (raw)
In-Reply-To: <CAB7JpEHq6rDS4=twUf7gito5zxinYiHZban77psKEQ962z0LYw@mail.gmail.com>
On Wed, Feb 27, 2013 at 09:08:11PM +0200, Alexander Shishkin wrote:
> On Feb 27, 2013 8:34 AM, "Peter Chen" <peter.chen@freescale.com> wrote:
> >
> > - For host, the vbus should always be on.
> > - For otg, the vbus is off defaultly, the vbus needs to be
> > turned on/off when usb role switches.
> >
> > + * @reg_vbus: used to control internal vbus regulator
> > */
> > struct ci13xxx {
> > struct device *dev;
> > @@ -172,6 +173,7 @@ struct ci13xxx {
> > struct usb_otg otg;
> > bool id_event;
> > bool b_sess_valid_event;
> > + struct regulator *reg_vbus;
> > };
>
> I suggest that this regulator be taken care of by either the platform code
> or phy layer, it doesn't look like it really belongs in chipidea core. The
> easiest way I guess would be to do something similar to the notify
> callback in msm platform code.
VBUS operation is typical operation during the USB code, eg, we need
to open vbus at Host mode, we need close/open vbus during host<->gadget
switch.
I suggest vbus regulator is specified at platform code, and assign it
to ci core's pdata, like sasche's patch pdata->dr_mode and pdata->phy_mode.
At core code, we can have a vbus operation API for on/off vbus if vbus
regulator is existed.
--
Best Regards,
Peter Chen
next prev parent reply other threads:[~2013-02-28 6:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 6:33 [PATCH v10 0/8] Add tested id switch and vbus connect detect support for Chipidea Peter Chen
2013-02-27 6:33 ` [PATCH v10 1/8] Revert "USB: chipidea: add vbus detect for udc" Peter Chen
2013-02-27 6:33 ` [PATCH v10 2/8] usb: chipidea: add otg file Peter Chen
2013-02-27 6:33 ` [PATCH v10 3/8] usb: chipidea: add otg id switch and vbus connect/disconnect detect Peter Chen
2013-02-27 6:33 ` [PATCH v10 4/8] usb: chipidea: udc: add pullup/pulldown dp at hw_device_state Peter Chen
[not found] ` <CAB7JpEFWMQaAS+tnR2Xd9OL+3eFeOp5ELLA92t55Vu0oMfKn7Q@mail.gmail.com>
2013-02-28 6:21 ` Peter Chen
2013-02-27 6:33 ` [PATCH v10 5/8] usb: chipidea: udc: retire the flag CI13_PULLUP_ON_VBUS Peter Chen
2013-02-27 6:33 ` [PATCH v10 6/8] usb: chipidea: imx: add internal vbus regulator control Peter Chen
2013-02-27 7:55 ` Felipe Balbi
2013-02-27 8:07 ` Sascha Hauer
2013-02-27 8:13 ` Peter Chen
2013-02-27 8:36 ` Felipe Balbi
2013-02-27 14:43 ` Darius Augulis
2013-03-04 11:13 ` Felipe Balbi
[not found] ` <CAB7JpEHq6rDS4=twUf7gito5zxinYiHZban77psKEQ962z0LYw@mail.gmail.com>
2013-02-27 20:42 ` Felipe Balbi
2013-02-28 6:06 ` Peter Chen [this message]
2013-02-28 7:29 ` Felipe Balbi
2013-02-28 8:24 ` Peter Chen
2013-02-27 6:33 ` [PATCH v10 7/8] usb: chipidea: udc: fix the oops when plugs in usb cable after rmmod gadget Peter Chen
2013-02-27 6:33 ` [PATCH v10 8/8] usb: chipidea: imx: fix the error that using uninitialized pointer Peter Chen
2013-02-27 12:39 ` Sergei Shtylyov
2013-02-28 3:24 ` Peter Chen
[not found] ` <CAB7JpEEuGP2Vo6HMZz30BZgiGQbBYqEVMRFEb7m0MbsC8oDjgQ@mail.gmail.com>
2013-02-28 3:34 ` Peter Chen
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=20130228060608.GD19387@nchen-desktop \
--to=peter.chen@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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