From: Kishon Vijay Abraham I <kishon@ti.com>
To: <gregkh@linuxfoundation.org>, <tony@atomide.com>,
<linux@arm.linux.org.uk>, <eballetbo@gmail.com>,
<javier@dowhile0.org>, <b-cousson@ti.com>, <balbi@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>
Cc: <kishon@ti.com>
Subject: [PATCH 0/5] ARM: OMAP: arm part of usb patches
Date: Wed, 6 Feb 2013 11:28:08 +0530 [thread overview]
Message-ID: <1360130294-5976-1-git-send-email-kishon@ti.com> (raw)
Hi Greg,
Here is the patch series that includes the arch/arm part to get MUSB
working in OMAP platforms. As discussed in the other mail thread with
Tony, this patch series should go into usb-next.
This patch series also contains a patch by Felipe to fix compilation
warning in usb-next when CONFIG_OMAP_CONTROL_USB is not set.
Boot tested panda board.
Felipe Balbi (1):
usb: omap_control_usb: fix compile warning
Kishon Vijay Abraham I (4):
ARM: OMAP4: remove control module address space from PHY and OTG
ARM: OMAP: devices: create device for usb part of control module
ARM: OMAP2: MUSB: Specify omap4 has mailbox
ARM: OMAP: USB: Add phy binding information
arch/arm/mach-omap2/board-2430sdp.c | 2 ++
arch/arm/mach-omap2/board-3430sdp.c | 2 ++
arch/arm/mach-omap2/board-4430sdp.c | 2 ++
arch/arm/mach-omap2/board-cm-t35.c | 2 ++
arch/arm/mach-omap2/board-devkit8000.c | 2 ++
arch/arm/mach-omap2/board-igep0020.c | 2 ++
arch/arm/mach-omap2/board-ldp.c | 2 ++
arch/arm/mach-omap2/board-omap3beagle.c | 2 ++
arch/arm/mach-omap2/board-omap3evm.c | 2 ++
arch/arm/mach-omap2/board-omap3logic.c | 2 ++
arch/arm/mach-omap2/board-omap3pandora.c | 2 ++
arch/arm/mach-omap2/board-omap3stalker.c | 2 ++
arch/arm/mach-omap2/board-omap3touchbook.c | 2 ++
arch/arm/mach-omap2/board-omap4panda.c | 2 ++
arch/arm/mach-omap2/board-overo.c | 2 ++
arch/arm/mach-omap2/board-rm680.c | 2 ++
arch/arm/mach-omap2/board-zoom-peripherals.c | 2 ++
arch/arm/mach-omap2/devices.c | 45 ++++++++++++++++++++++++++
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 13 --------
arch/arm/mach-omap2/usb-musb.c | 3 ++
include/linux/usb/musb.h | 2 ++
include/linux/usb/omap_control_usb.h | 2 +-
22 files changed, 85 insertions(+), 14 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-02-06 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 5:58 Kishon Vijay Abraham I [this message]
2013-02-06 5:58 ` [PATCH 1/5] ARM: OMAP4: remove control module address space from PHY and OTG Kishon Vijay Abraham I
2013-02-06 5:58 ` [PATCH 2/5] ARM: OMAP: devices: create device for usb part of control module Kishon Vijay Abraham I
2013-02-06 13:01 ` Sergei Shtylyov
2013-02-06 5:58 ` [PATCH 3/5] ARM: OMAP2: MUSB: Specify omap4 has mailbox Kishon Vijay Abraham I
2013-02-06 10:57 ` Russell King - ARM Linux
2013-02-06 11:03 ` Felipe Balbi
2013-02-06 11:22 ` Felipe Balbi
2013-02-06 11:36 ` Russell King - ARM Linux
2013-02-06 5:58 ` [PATCH 4/5] ARM: OMAP: USB: Add phy binding information Kishon Vijay Abraham I
2013-02-06 5:58 ` [PATCH 5/5] usb: omap_control_usb: fix compile warning 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=1360130294-5976-1-git-send-email-kishon@ti.com \
--to=kishon@ti.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=eballetbo@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=javier@dowhile0.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox