linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (s.hauer at pengutronix.de)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/7] ARM: mx28: add usb host function
Date: Fri, 5 Aug 2011 18:52:51 +0200	[thread overview]
Message-ID: <20110805165250.GJ31404@pengutronix.de> (raw)
In-Reply-To: <20110805142252.GA12405@nchen-desktop>

On Fri, Aug 05, 2011 at 10:22:54PM +0800, Peter Chen wrote:
> On Fri, Aug 05, 2011 at 03:03:01PM +0200, s.hauer at pengutronix.de wrote:
> > On Fri, Aug 05, 2011 at 07:53:21AM +0000, Lin Tony-B19295 wrote:
> > > Any comments for the patch series?
> > 
> > Yes. The way you handle the USB phys is totally inacceptable. Please
> > understand that there are *two* devices, one is the ehci core and the
> > other is the associated phy.
> > 
> > You need to register the phy as a platform device, the corresponding
> > driver then has to register the phy using some kind of usb_transceiver_register().
> > On the ehci side the mxc-ehci driver has to find its phy using
> > usb_get_transceiver().
> > 
> > Note that the infrastructure needed for this is not in the kernel, but
> > there are patches recently posted on linux-usb:
> > 
> > http://www.spinics.net/lists/linux-usb/msg50148.html
> > 
> > Sascha
> > 
> I have discussed with Heikki, his framework is good, it saperates phys from
> otg driver, so phy's utilities can be called at both otg and
> device only mode, besides it can support usb charger better.
> 
> So, do we pause i.mx28 usb's upstream until Heikki's otg modification in
> master, or just do thing like ulpi.c?

I think you can use Heikkis patches as a base. They will get updates
before hitting mainline, but the changes to the (phy-) driver side
should be trivial. This way we can also detect possible problems with
Heikkis patches. There's plenty of time before the next merge window to
get the patches into shape.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2011-08-05 16:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02  8:39 [PATCH v4 0/7] ARM: mx28: add usb host function Tony Lin
2011-08-02  8:39 ` [PATCH v4 1/7] ARM: mxs: ehci: consolidate definitions and structures to share among platforms Tony Lin
2011-08-02  8:39 ` [PATCH v4 2/7] ARM: mxs: make ehci-mxc more flexible to be used on different platforms Tony Lin
2011-08-02  8:39 ` [PATCH v4 3/7] ARM: mxs: add usb clocks to clock tree Tony Lin
2011-08-02  8:39 ` [PATCH v4 4/7] ARM: mxs: enable usb phy power supply Tony Lin
2011-08-02  8:39 ` [PATCH v4 5/7] ARM: mxs: add usb platform operations Tony Lin
2011-08-02  8:39 ` [PATCH v4 6/7] " Tony Lin
2011-08-02  8:39 ` [PATCH v4 7/7] ARM: mxs: add usb host function to default config Tony Lin
2011-08-05  7:53 ` [PATCH v4 0/7] ARM: mx28: add usb host function Lin Tony-B19295
2011-08-05 13:03   ` s.hauer at pengutronix.de
2011-08-05 14:22     ` Peter Chen
2011-08-05 16:52       ` s.hauer at pengutronix.de [this message]
2011-08-08  2:03         ` Lin Tony-B19295

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=20110805165250.GJ31404@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).