From: Alexander Holler <holler@ahsoftware.de>
To: balbi@ti.com
Cc: Roger Quadros <rogerq@ti.com>,
Greg KH <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] USB: ehci-omap: Select USB_PHY
Date: Fri, 12 Apr 2013 02:22:13 +0200 [thread overview]
Message-ID: <516753B5.2040002@ahsoftware.de> (raw)
In-Reply-To: <20130411182946.GA20264@arwen.pp.htv.fi>
Am 11.04.2013 20:29, schrieb Felipe Balbi:
> and who said OMAP USB depends on CONFIG_USB_PHY ? Some platforms need to
> control a PHY and some don't.
I've read that so.
> Go check out kernel 2.6.39 (maybe even 3.1 and 3.2) and you'll see that
> we're much better off today where we can actually have multiple PHY
> drivers and multiple UDC drivers enabled (either as modules or
> built-in), but the fact is that changing all of this over takes time and
> sometimes people make mistakes, but that's alright, since we have the
> -rc series to catch those unwanted errors.
I'll still have to stick to 3.2 because nothing afterwards boots from
EHCI on my beagleboard.
>
> Without the help of the rest of the community, though, it'll just get
> slower and slower. With the whole single zImage effort going on in the
> ARM land, things have gotten much more critical WRT getting rid of
> "selects" and turning legacy "drivers" into real drivers, not just a
> bunch of exported functions which a single architecture uses.
>
> Add to that all the rework going on in the Gadget Framework, PHY layer
> and EHCI drivers (which now has a core re-usable library thanks to Alan
> Stern) and you have a lot of work to do.
>
> Next time you consider ranting about something, use that 'frustration'
> and turn it into motivation to write patches, then we all win. Also
I frequently tried and gave up. But thanks for the good suggestions.
Regards,
Alexander
next prev parent reply other threads:[~2013-04-12 0:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 9:42 [PATCH] USB: ehci-omap: Select USB_PHY Roger Quadros
2013-04-11 10:04 ` Felipe Balbi
2013-04-11 10:51 ` Roger Quadros
2013-04-11 10:51 ` Roger Quadros
2013-04-11 10:55 ` Felipe Balbi
2013-04-11 10:55 ` Felipe Balbi
2013-04-11 12:42 ` Roger Quadros
2013-04-11 12:42 ` Roger Quadros
2013-04-11 13:02 ` Alexander Holler
2013-04-11 14:44 ` Roger Quadros
2013-04-11 14:44 ` Roger Quadros
2013-04-11 15:02 ` Felipe Balbi
2013-04-11 15:02 ` Felipe Balbi
2013-04-11 17:33 ` Alexander Holler
2013-04-11 18:29 ` Felipe Balbi
2013-04-11 18:29 ` Felipe Balbi
2013-04-12 0:22 ` Alexander Holler [this message]
2013-04-11 13:18 ` Roger Quadros
2013-04-11 13:18 ` Roger Quadros
[not found] ` <5166B829.1020304-l0cyMroinI0@public.gmane.org>
2013-04-11 14:34 ` Felipe Balbi
2013-04-11 14:34 ` Felipe Balbi
2013-04-11 14:53 ` Roger Quadros
2013-04-11 14:53 ` Roger Quadros
2013-04-11 15:09 ` Felipe Balbi
2013-04-11 15:09 ` Felipe Balbi
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=516753B5.2040002@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=stern@rowland.harvard.edu \
/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.