From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Clean up legacy platform data handling for omaps for v3.13
Date: Fri, 20 Sep 2013 10:38:09 -0700 [thread overview]
Message-ID: <20130920173310.2584.24522.stgit@localhost> (raw)
Hi all,
Here are few patches to make it easier for us to maintain
legacy platform data support while moving to device
tree based booting. It seems that we still have quite a
few places where we still need platform data for omap3
to keep things from breaking.
As the remaining drivers get converted to use device tree,
we can then just remove the support from the pdata-quirks.c.
Regards,
Tony
---
Tony Lindgren (4):
ARM: OMAP2+: Always build in board-generic
ARM: OMAP2+: Add quirk support for legacy platform data init
ARM: OMAP2+: Use pdata quirk support for board-generic.c
ARM: OMAP2+: Use pdata quirks for wl12xx legacy init
arch/arm/mach-omap2/Kconfig | 10 +--
arch/arm/mach-omap2/Makefile | 2 -
arch/arm/mach-omap2/board-generic.c | 33 ----------
arch/arm/mach-omap2/common.h | 2 +
arch/arm/mach-omap2/devices.c | 38 ------------
arch/arm/mach-omap2/pdata-quirks.c | 111 +++++++++++++++++++++++++++++++++++
6 files changed, 118 insertions(+), 78 deletions(-)
create mode 100644 arch/arm/mach-omap2/pdata-quirks.c
--
Signature
next reply other threads:[~2013-09-20 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 17:38 Tony Lindgren [this message]
2013-09-20 17:38 ` [PATCH 1/4] ARM: OMAP2+: Always build in board-generic Tony Lindgren
2013-09-20 17:38 ` [PATCH 2/4] ARM: OMAP2+: Add quirk support for legacy platform data init Tony Lindgren
2013-09-20 17:38 ` [PATCH 3/4] ARM: OMAP2+: Use pdata quirk support for board-generic.c Tony Lindgren
2013-09-20 17:38 ` [PATCH 4/4] ARM: OMAP2+: Use pdata quirks for wl12xx legacy init Tony Lindgren
2013-09-25 23:26 ` Tony Lindgren
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=20130920173310.2584.24522.stgit@localhost \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).