From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] usb: musb: fix USB enumeration issue in OMAP3 platform
Date: Mon, 8 Jul 2013 16:44:13 +0530 [thread overview]
Message-ID: <1373282057-20181-1-git-send-email-kishon@ti.com> (raw)
This series fixes the USB enumeration issue caused because of the controller
not able to get a reference to the PHY because of incorrect binding in the
board file.
In the case of non-dt boot, the platform specific initialization file
(board file) will do usb_bind_phy that binds the usb controller with the
PHY using device names. After the device names are created using
PLATFORM_DEVID_AUTO, our original method of binding by device names doesn't
work reliably (since the device name changes). Hence the usb controller
is made to use labels for getting the PHY.
Here the PHY name is added in the plat data of USB controller device which
should be used by the controller driver to get the PHY.
Two new APIs usb_get_phy_by_name and devm_usb_get_phy_by_name are added to
be used by the controller to get the PHY by name.
Changes from v1:
*) Rebased to the latest mainline kernel
Changes from RFC
*) Changed the signature of usb_get_phy_by_name() not to use struct device *
Kishon Vijay Abraham I (4):
arm: omap: Add phy binding info for musb in plat data
usb: phy: add a new API to get PHY ref by label
usb: musb: omap: use the new API to get PHY reference by label
arm: omap: remove using usb_bind_phy for binding musb and phy
arch/arm/mach-omap2/board-2430sdp.c | 1 -
arch/arm/mach-omap2/board-3430sdp.c | 1 -
arch/arm/mach-omap2/board-cm-t35.c | 1 -
arch/arm/mach-omap2/board-devkit8000.c | 1 -
arch/arm/mach-omap2/board-igep0020.c | 1 -
arch/arm/mach-omap2/board-ldp.c | 1 -
arch/arm/mach-omap2/board-omap3beagle.c | 1 -
arch/arm/mach-omap2/board-omap3evm.c | 1 -
arch/arm/mach-omap2/board-omap3logic.c | 1 -
arch/arm/mach-omap2/board-omap3pandora.c | 1 -
arch/arm/mach-omap2/board-omap3stalker.c | 1 -
arch/arm/mach-omap2/board-omap3touchbook.c | 1 -
arch/arm/mach-omap2/board-overo.c | 1 -
arch/arm/mach-omap2/board-rm680.c | 1 -
arch/arm/mach-omap2/board-rx51.c | 1 -
arch/arm/mach-omap2/board-zoom-peripherals.c | 1 -
arch/arm/mach-omap2/usb-musb.c | 3 +
drivers/usb/musb/musb_core.c | 1 +
drivers/usb/musb/musb_core.h | 1 +
drivers/usb/musb/omap2430.c | 2 +-
drivers/usb/phy/phy.c | 77 ++++++++++++++++++++++++++
include/linux/usb/musb.h | 3 +
include/linux/usb/phy.h | 14 +++++
23 files changed, 100 insertions(+), 17 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-07-08 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 11:14 Kishon Vijay Abraham I [this message]
2013-07-08 11:14 ` [PATCH v2 1/4] arm: omap: Add phy binding info for musb in plat data Kishon Vijay Abraham I
2013-07-16 12:44 ` Tony Lindgren
2013-07-08 11:14 ` [PATCH v2 2/4] usb: phy: add a new API to get PHY ref by label Kishon Vijay Abraham I
2013-07-08 11:14 ` [PATCH v2 3/4] usb: musb: omap: use the new API to get PHY reference " Kishon Vijay Abraham I
2013-07-08 11:14 ` [PATCH v2 4/4] arm: omap: remove using usb_bind_phy for binding musb and phy Kishon Vijay Abraham I
2013-07-16 12:46 ` Tony Lindgren
2013-07-16 5:52 ` [PATCH v2 0/4] usb: musb: fix USB enumeration issue in OMAP3 platform Kishon Vijay Abraham I
2013-07-16 12:42 ` Felipe Balbi
2013-07-16 12:47 ` Tony Lindgren
2013-07-19 8:45 ` Kishon Vijay Abraham I
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=1373282057-20181-1-git-send-email-kishon@ti.com \
--to=kishon@ti.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;
as well as URLs for NNTP newsgroup(s).