From: Magnus Damm <magnus.damm@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: devel@driverdev.osuosl.org, linux-sh@vger.kernel.org,
gregkh@linuxfoundation.org, horms@verge.net.au,
geert@linux-m68k.org, laurent.pinchart@ideasonboard.com,
olof@lixom.net, Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH 00/03] staging: Emma Mobile USB driver and KZM9D board code
Date: Thu, 22 May 2014 08:53:39 +0000 [thread overview]
Message-ID: <20140522085339.26279.83340.sendpatchset@w520> (raw)
Emma Mobile USB driver and KZM9D board code
[PATCH 01/03] staging: emxx_udc: Add Emma Mobile USB Gadget driver
[PATCH 02/03] staging: emxx_udc: I/O memory and IRQ resource support
[PATCH 03/03] staging: board: kzm9d: Board staging support for emxx_udc
This patch series contains an old USB Gadget driver for Emma Mobile
that gets slightly adjusted to make use of the platform device interface
which in turn is used to add USB Gadget support to the KZM9D board.
Two separate staging components are included in this series:
1) the emxx_udc driver - from out-of-tree Android 2.6.35.7
2) board staging support for KZM9D - platform device for DT-only KZM9D
The two components above will be used to continously improve the driver
and board integration code until the driver can be moved out of staging
and/or DT bindings are available so the board staging platform device code
can be replaced with a DT node.
Olof, patch 3/3 contains some board staging code for KZM9D. As it is
today the EMEV2 SoC is DT-only and we neither have defconfig nor Kconfig
definitions for the KZM9D board (emev2-kzm9d.dts). Instead of again adding
board code to the ARM subarchitecture I hereby propose that we use staging to
integrate non-DT drivers while they are improved to get DT support.
Greg, please let me know your opinions. I'd be happy to rework the code.
Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
Written against renesas-devel-v3.15-rc5-20140521
drivers/staging/Kconfig | 4
drivers/staging/Makefile | 2
drivers/staging/board/Kconfig | 7
drivers/staging/board/Makefile | 1
drivers/staging/board/board.h | 17
drivers/staging/board/kzm9d.c | 18
drivers/staging/emxx_udc/Kconfig | 10
drivers/staging/emxx_udc/Makefile | 1
drivers/staging/emxx_udc/emxx_udc.c | 3616 ++++++++++++++++++++++++++++++++++-
drivers/staging/emxx_udc/emxx_udc.h | 671 ++++++
10 files changed, 4299 insertions(+), 48 deletions(-)
next reply other threads:[~2014-05-22 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 8:53 Magnus Damm [this message]
2014-05-22 8:53 ` [PATCH 02/03] staging: emxx_udc: I/O memory and IRQ resource support Magnus Damm
2014-05-22 8:54 ` [PATCH 03/03] staging: board: kzm9d: Board staging support for emxx_udc Magnus Damm
2014-05-22 9:19 ` Geert Uytterhoeven
2014-05-22 9:29 ` Magnus Damm
2014-05-22 9:17 ` [PATCH 00/03] staging: Emma Mobile USB driver and KZM9D board code Dan Carpenter
2014-05-22 9:32 ` Magnus Damm
2014-05-23 2:20 ` Greg KH
2014-05-22 9:21 ` Geert Uytterhoeven
2014-05-22 9:32 ` Magnus Damm
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=20140522085339.26279.83340.sendpatchset@w520 \
--to=magnus.damm@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=olof@lixom.net \
/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).