From: Marc Zyngier <marc.zyngier@arm.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Magnus Damm <damm+renesas@opensource.se>,
Arnd Bergmann <arnd@arndb.de>,
Simon Horman <horms+renesas@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
<devel@driverdev.osuosl.org>, <devicetree@vger.kernel.org>,
<linux-pm@vger.kernel.org>, <linux-sh@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH/RFC 0/6] staging: board: armadillo800eva: Board staging for sh_mobile_lcdc_fb
Date: Mon, 06 Apr 2015 11:23:14 +0100 [thread overview]
Message-ID: <9cb05c4e687de35ada0b83fe816393c8@www.loen.fr> (raw)
In-Reply-To: <1428064923-24950-1-git-send-email-geert+renesas@glider.be>
Hi Geert,
On 2015-04-03 13:41, Geert Uytterhoeven wrote:
> 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."),
Please allow me a semantic correction here: this commit never broke
anything. It merely revealed how platform code (OMAP, iMX6, shmobile)
abused the irq_domain subsystem, hoping to get away with only a partial
conversion to DT. The platform code itself was broken from the moment it
used DT to discover its interrupt controller.
The truth is, it is not possible to sanely convert bits of a platform
to DT. The changes creep into all the subsystems, and doing it in stages
requires tons of ugly hacks (and I've written my share of them).
That being said, I'm off reviewing these two matches.
Thanks,
M.
--
Fast, cheap, reliable. Pick two.
prev parent reply other threads:[~2015-04-06 10:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 12:41 Geert Uytterhoeven
2015-04-03 12:41 ` [PATCH 1/6] Revert "staging: board: disable as it breaks the build" Geert Uytterhoeven
2015-04-06 0:40 ` Simon Horman
2015-04-07 13:16 ` Geert Uytterhoeven
2015-04-08 0:44 ` Simon Horman
2015-04-03 12:41 ` [PATCH/RFC 2/6] staging: board: Initialize staging board code earlier Geert Uytterhoeven
2015-04-03 12:42 ` [PATCH/RFC 3/6] staging: board: Add support for translating hwirq to virq numbers Geert Uytterhoeven
2015-04-06 10:45 ` Marc Zyngier
2015-04-03 12:42 ` [PATCH/RFC 4/6] staging: board: kzm9d: Translate hwirq numbers " Geert Uytterhoeven
2015-04-03 12:42 ` [PATCH/RFC 5/6] staging: board: Add support for devices with complex dependencies Geert Uytterhoeven
2015-04-03 12:57 ` Dan Carpenter
2015-04-03 13:27 ` Geert Uytterhoeven
2015-04-03 17:07 ` Russell King - ARM Linux
2015-04-03 17:04 ` Russell King - ARM Linux
2015-04-05 8:55 ` Geert Uytterhoeven
2015-04-04 12:46 ` Laurent Pinchart
2015-04-05 9:00 ` Geert Uytterhoeven
2015-04-05 20:06 ` Laurent Pinchart
2015-04-03 12:42 ` [PATCH/RFC 6/6] staging: board: armadillo800eva: Board staging for sh_mobile_lcdc_fb Geert Uytterhoeven
2015-04-03 16:24 ` [PATCH/RFC 0/6] " Laurent Pinchart
2015-04-03 19:35 ` Geert Uytterhoeven
2015-04-06 10:23 ` Marc Zyngier [this message]
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=9cb05c4e687de35ada0b83fe816393c8@www.loen.fr \
--to=marc.zyngier@arm.com \
--cc=arnd@arndb.de \
--cc=damm+renesas@opensource.se \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=horms+renesas@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@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
all inboxes | Powered by JetHome®