From: Magnus Damm <magnus.damm@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: devel@driverdev.osuosl.org, pebolle@tiscali.nl,
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>,
dan.carpenter@oracle.com
Subject: [PATCH v3 05/05] staging: board: kzm9d: Board staging support for emxx_udc
Date: Fri, 06 Jun 2014 10:44:52 +0000 [thread overview]
Message-ID: <20140606104452.4423.16947.sendpatchset@w520> (raw)
In-Reply-To: <20140606104408.4423.36098.sendpatchset@w520>
From: Magnus Damm <damm+renesas@opensource.se>
Add staging board support for the KZM9D board and add
an emxx_udc platform device to allow in-tree continous
development of the driver on the KZM9D board.
When DT bindings are ready for the emxx_udc driver then
the platform device in the KZM9D staging board code can
easily be removed. Until then we use platform devices
to continously improve the driver and integration code.
Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
Changes since V2:
- None
Changes since V1:
- Broke out staging board base patch
- Compile in if CONFIG_ARCH_EMEV2 is selected
- Make use of board_staging_dt_node_available()
drivers/staging/board/Makefile | 1 +
drivers/staging/board/kzm9d.c | 19 +++++++++++++++++++
2 files changed, 20 insertions(+)
--- 0011/drivers/staging/board/Makefile
+++ work/drivers/staging/board/Makefile 2014-05-29 21:40:49.000000000 +0900
@@ -1 +1,2 @@
obj-y := board.o
+obj-$(CONFIG_ARCH_EMEV2) += kzm9d.o
--- /dev/null
+++ work/drivers/staging/board/kzm9d.c 2014-05-29 21:42:34.000000000 +0900
@@ -0,0 +1,19 @@
+/* Staging board support for KZM9D. Enable not-yet-DT-capable devices here. */
+
+#include <linux/kernel.h>
+#include <linux/platform_device.h>
+#include "board.h"
+
+static const struct resource usbs1_res[] __initconst = {
+ DEFINE_RES_MEM(0xe2800000, 0x2000),
+ DEFINE_RES_IRQ(159),
+};
+
+static void __init kzm9d_init(void)
+{
+ if (!board_staging_dt_node_available(usbs1_res, ARRAY_SIZE(usbs1_res)))
+ platform_device_register_simple("emxx_udc", -1, usbs1_res,
+ ARRAY_SIZE(usbs1_res));
+}
+
+board_staging("renesas,kzm9d", kzm9d_init);
next prev parent reply other threads:[~2014-06-06 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 10:44 [PATCH v3 00/05] staging: Emma Mobile USB driver and KZM9D board code V3 Magnus Damm
2014-06-06 10:44 ` [PATCH v3 02/05] staging: emxx_udc: I/O memory and IRQ resource support Magnus Damm
2014-06-06 10:44 ` [PATCH v3 03/05] staging: emxx_udc: Add TODO file Magnus Damm
2014-06-06 10:44 ` [PATCH v3 04/05] staging: board: Initial board staging support Magnus Damm
2014-06-06 10:44 ` Magnus Damm [this message]
2014-06-06 15:39 ` [PATCH v3 00/05] staging: Emma Mobile USB driver and KZM9D board code V3 Greg KH
2014-06-09 5:14 ` Magnus Damm
2014-06-10 1:57 ` Simon Horman
[not found] ` <20140606104417.4423.38999.sendpatchset@w520>
2014-06-20 8:22 ` [PATCH v3 01/05] staging: emxx_udc: Add Emma Mobile USB Gadget driver Paul Bolle
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=20140606104452.4423.16947.sendpatchset@w520 \
--to=magnus.damm@gmail.com \
--cc=dan.carpenter@oracle.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 \
--cc=pebolle@tiscali.nl \
/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).