[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1428064923-24950-1-git-send-email-geert+renesas@glider.be>
Date: Fri, 3 Apr 2015 14:41:57 +0200
From: Geert Uytterhoeven <geert+renesas@...der.be>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Magnus Damm <damm+renesas@...nsource.se>,
Arnd Bergmann <arnd@...db.de>,
Simon Horman <horms+renesas@...ge.net.au>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
Cc: Marc Zyngier <marc.zyngier@....com>, devel@...verdev.osuosl.org,
linux-sh@...r.kernel.org, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Geert Uytterhoeven <geert+renesas@...der.be>
Subject: [PATCH/RFC 0/6] staging: board: armadillo800eva: Board staging for sh_mobile_lcdc_fb
Hi all,
This RFC patch series adds board staging support for r8a7740/armadillo.
For now this supports only the frame buffer device for the on-board LCD.
The goal is to complete the move to ARM multiplatform kernels for all
shmobile platforms, and drop the existing board files
(arch/arm/mach-shmobile/board-*).
The board staging area was introduced last year to allow continuous
upstream in-tree development and integration of platform devices. It
helps developers integrate devices as platform devices for device
drivers that only provide platform device bindings. This in turn allows
for incremental development of both hardware feature support and DT
binding work in parallel.
This series consists of 4 parts:
- Patch 1 re-enables compilation of the board staging area, which was
disabled after a compile breakage, but has been fixed in the mean
time,
- Path 2 moves initialization of staging board code to an earlier
moment, as currently it happens after unused PM domains are powered
down,
- Patches 3 and 4 (hopefully) fix the existing kzm9d board staging
code, which was presumably broken by commit 9a1091ef0017c40a
("irqchip: gic: Support hierarchy irq domain."),
- Patches 5 and 6 add support for registering platform devices with
complex dependencies (clocks, pinctrl, gpios, PM domains), and add
armadillo board staging code for enabling a frame buffer on the
on-board LCD.
Questions:
- Are there other devices from board-armadillo.c that work fine in
armadillo-legacy, and that we want to add?
I think this is the list of devices lacking DT support and/or
missing in DTS:
- renesas_usbhs (does this work? the platform device is
instantiated conditionally, but the condition (gpio state) is
never true?)
- sh-mobile-hdmi/sh_mobile_lcdc_fb.1 (this seems to be broken in
-legacy?)
- sdhi1 (we do have sdhi0)
- mmcif
- soc-camera-pdrv/sh_mobile_ceu
- ipmmu
- sh-dma-engine (this will probably never get DT support)
- What about support for other boards (kzm9g, bockw, marzen)?
This was tested on r8a7740/armadillo.
This was not tested on emev2/kzm9d, due to lack of hardware.
Thanks for your comments!
Geert Uytterhoeven (6):
Revert "staging: board: disable as it breaks the build"
[RFC] staging: board: Initialize staging board code earlier
[RFC] staging: board: Add support for translating hwirq to virq numbers
[RFC] staging: board: kzm9d: Translate hwirq numbers to virq numbers
[RFC] staging: board: Add support for devices with complex dependencies
[RFC] staging: board: armadillo800eva: Board staging for sh_mobile_lcdc_fb
drivers/staging/board/Kconfig | 1 -
drivers/staging/board/Makefile | 3 +-
drivers/staging/board/armadillo800eva.c | 124 ++++++++++++++++++++++++++++
drivers/staging/board/board.c | 142 ++++++++++++++++++++++++++++++++
drivers/staging/board/board.h | 38 ++++++++-
drivers/staging/board/kzm9d.c | 10 ++-
6 files changed, 313 insertions(+), 5 deletions(-)
create mode 100644 drivers/staging/board/armadillo800eva.c
--
1.9.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists