From: George Cherian <george.cherian@ti.com>
To: balbi@ti.com
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
George Cherian <george.cherian@ti.com>
Subject: [PATCH 0/3] Adding AM437x support to dwc3-omap glue
Date: Mon, 27 May 2013 13:32:54 +0530 [thread overview]
Message-ID: <1369641777-4509-1-git-send-email-george.cherian@ti.com> (raw)
Initial patch set to add support for dwc3 in am437x platform.
This patch series addresses the regiter map differences between
OMAP5 and AM437x, to re-use the same driver.
AM437x and OMAP5 dwc3 subsytem have different register map.
Major differences are as follows.
OMAP5 has one main interrupt and one misc interrupt
Aegis has four main interrupts and one misc interrupt.
Miscellanous Interrupt offsets are changed.
UTMI OTG Control and Status Registers offsets are changed.
DEBUG Configuration and Status Registers are changed.
The main intend of the patch is to re-use the same wrapper driver
for both OMAP5 and AM437x, by using the x_major in revision
register and adjusting the offsets.
George Cherian (3):
usb: dwc3: omap: Adding am437x specific register map changes
usb: dwc3: omap: Intialize the register offset values for OMAP5 and
AM437x
usb: dwc3: omap Modify dwc3_omap_readl/writel with offsets
drivers/usb/dwc3/dwc3-omap.c | 183 ++++++++++++++++++++++++++++++-------------
1 file changed, 128 insertions(+), 55 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-05-27 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 8:02 George Cherian [this message]
2013-05-27 8:02 ` [PATCH 1/3] usb: dwc3: omap: Adding am437x specific register map changes George Cherian
2013-05-27 8:02 ` [PATCH 2/3] usb: dwc3: omap: Intialize the register offset values for OMAP5 and AM437x George Cherian
2013-05-27 8:02 ` [PATCH 3/3] usb: dwc3: omap Modify dwc3_omap_readl/writel with offsets George Cherian
2013-05-28 17:32 ` Felipe Balbi
2013-05-29 6:54 ` Cherian, George
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=1369641777-4509-1-git-send-email-george.cherian@ti.com \
--to=george.cherian@ti.com \
--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 \
/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).