From: Kevin Cernekee <cernekee@gmail.com>
To: ralf@linux-mips.org
Cc: <ffainelli@freebox.fr>, <mbizon@freebox.fr>,
<jonas.gorski@gmail.com>, <linux-mips@linux-mips.org>
Subject: [PATCH 0/7] Prerequisites for BCM63XX UDC driver
Date: Fri, 22 Jun 2012 22:14:50 -0700 [thread overview]
Message-ID: <0f67eabbb0d5c59add27e42a08b94944@localhost> (raw)
These patches are intended to lay the groundwork for a new USB Device
Controller (gadget UDC) driver. arch/mips/bcm63xx updates include:
Clock enable bits
DMA descriptor updates
New register and IRQ definitions
Create platform_device and platform_data
Baseline is:
git://git.linux-mips.org/pub/scm/ralf/upstream-sfr.git #mips-for-linux-next
Note that this is not an OTG-capable controller. Therefore, boards are
permanently wired up for either host mode or device mode. Device vs.
host can be determined in board_bcm963xx.c based on the detected board ID.
Some boards have connectors/pads for both modes, but need to be
reworked to run in device mode; usually this involves moving 0-ohm
resistors on the D+ and D- lines.
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Cernekee <cernekee@gmail.com>
To: ralf@linux-mips.org
Cc: ffainelli@freebox.fr, mbizon@freebox.fr, jonas.gorski@gmail.com,
linux-mips@linux-mips.org
Subject: [PATCH 0/7] Prerequisites for BCM63XX UDC driver
Date: Fri, 22 Jun 2012 22:14:50 -0700 [thread overview]
Message-ID: <0f67eabbb0d5c59add27e42a08b94944@localhost> (raw)
Message-ID: <20120623051450.Y_G4zIAZgp3upOg2uUqqJXRlxumsOZQhyu9dZ--FxFc@z> (raw)
These patches are intended to lay the groundwork for a new USB Device
Controller (gadget UDC) driver. arch/mips/bcm63xx updates include:
Clock enable bits
DMA descriptor updates
New register and IRQ definitions
Create platform_device and platform_data
Baseline is:
git://git.linux-mips.org/pub/scm/ralf/upstream-sfr.git #mips-for-linux-next
Note that this is not an OTG-capable controller. Therefore, boards are
permanently wired up for either host mode or device mode. Device vs.
host can be determined in board_bcm963xx.c based on the detected board ID.
Some boards have connectors/pads for both modes, but need to be
reworked to run in device mode; usually this involves moving 0-ohm
resistors on the D+ and D- lines.
next reply other threads:[~2012-06-23 5:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 5:14 Kevin Cernekee [this message]
2012-06-23 5:14 ` [PATCH 0/7] Prerequisites for BCM63XX UDC driver Kevin Cernekee
2012-06-23 5:14 ` [PATCH 1/7] MIPS: BCM63XX: Expose the USBH/USBD clocks on BCM6328/BCM6368 Kevin Cernekee
2012-06-23 5:14 ` Kevin Cernekee
2012-06-23 5:14 ` [PATCH 2/7] MIPS: BCM63XX: Move DMA descriptor definition into common header file Kevin Cernekee
2012-06-23 5:14 ` Kevin Cernekee
2012-06-26 15:13 ` Jonas Gorski
2012-06-23 5:14 ` [PATCH 3/7] MIPS: BCM63XX: Add new IUDMA definitions needed for USBD Kevin Cernekee
2012-06-23 5:14 ` Kevin Cernekee
2012-06-23 5:14 ` [PATCH 4/7] MIPS: BCM63XX: Add register definitions for USBD dependencies Kevin Cernekee
2012-06-23 5:14 ` Kevin Cernekee
2012-06-23 5:14 ` [PATCH 5/7] MIPS: BCM63XX: Fix USB IRQ definitions for 6328 Kevin Cernekee
2012-06-23 5:14 ` Kevin Cernekee
2012-06-23 5:14 ` [PATCH 6/7] MIPS: BCM63XX: Add register and IRQ definitions for USB 2.0 device Kevin Cernekee
2012-06-23 5:14 ` Kevin Cernekee
2012-06-23 5:14 ` [PATCH 7/7] MIPS: BCM63XX: Create platform_device for USBD Kevin Cernekee
2012-06-23 5:14 ` Kevin Cernekee
2012-07-09 2:58 ` [PATCH 0/7] Prerequisites for BCM63XX UDC driver Kevin Cernekee
2012-07-12 8:57 ` Jonas Gorski
2012-07-12 9:43 ` Florian Fainelli
2012-08-30 18:11 ` John Crispin
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=0f67eabbb0d5c59add27e42a08b94944@localhost \
--to=cernekee@gmail.com \
--cc=ffainelli@freebox.fr \
--cc=jonas.gorski@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=mbizon@freebox.fr \
--cc=ralf@linux-mips.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