From: pali.rohar@gmail.com (Pali Rohár)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP2+: Drop legacy board file for n900
Date: Wed, 15 Jun 2016 12:55:52 +0200 [thread overview]
Message-ID: <20160615105552.GN29844@pali> (raw)
In-Reply-To: <1465987689-14812-2-git-send-email-tony@atomide.com>
On Wednesday 15 June 2016 03:48:08 Tony Lindgren wrote:
> Let's drop the last two remaining omap3 legacy boot board files.
> Let's only use the device tree based booting known to work for
> these two boards.
>
> We still have two omap3 boards booting in legacy mode in addition
> to device tree based booting. All the other ten or so omap2+ SoCs
> have been booting using device tree mode only for years now. This
> has allowed us to get rid of quite a bit of arch/arm/mach-omap2
> related platform init code in favor of dts and driver changes.
>
> Pretty much the only remaining known users for omap3 legacy boot
> board files are Kevin's and Russell's boot test systems, and N900
> kernel tree maintained by Pali and Ivaylo. And all of them are
> also supporting the device tree based booting. The legacy booting
> mode has been kept around mostly to verify against regressions.
>
> As there is still a slim chance of possible other uses of the
> mainline kernel for these boards, let's just drop the board
> files for v4.8, and let's not touch the related platform init
> code until around v4.9 time if no issues are found. This makes
> it trivial for us to add back the board files with a simple revert.
>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
> arch/arm/mach-omap2/Kconfig | 6 -
> arch/arm/mach-omap2/Makefile | 3 -
> arch/arm/mach-omap2/board-rx51-peripherals.c | 1317 --------------------------
> arch/arm/mach-omap2/board-rx51-video.c | 67 --
> arch/arm/mach-omap2/board-rx51.c | 141 ---
> arch/arm/mach-omap2/board-rx51.h | 11 -
> 6 files changed, 1545 deletions(-)
> delete mode 100644 arch/arm/mach-omap2/board-rx51-peripherals.c
> delete mode 100644 arch/arm/mach-omap2/board-rx51-video.c
> delete mode 100644 arch/arm/mach-omap2/board-rx51.c
> delete mode 100644 arch/arm/mach-omap2/board-rx51.h
Hi! I just quickly looked at N900 status matrix https://elinux.org/N900
and there is still one thing not finished in DT: It is slot-name for
omap_hsmmc driver. So switch from legacy board code to DT is regression.
--
Pali Roh?r
pali.rohar at gmail.com
next prev parent reply other threads:[~2016-06-15 10:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 10:48 [PATCH 0/2] Drop last two remaining omap3 legacy board files Tony Lindgren
2016-06-15 10:48 ` [PATCH 1/2] ARM: OMAP2+: Drop legacy board file for n900 Tony Lindgren
2016-06-15 10:55 ` Pali Rohár [this message]
2016-06-15 11:02 ` Tony Lindgren
2016-06-15 11:49 ` Pali Rohár
2016-06-15 12:05 ` Tony Lindgren
2016-06-21 11:25 ` Tony Lindgren
2016-06-21 11:29 ` Pali Rohár
2016-06-21 11:32 ` Tony Lindgren
2016-06-22 16:48 ` Pali Rohár
2016-06-22 17:59 ` Pavel Machek
2016-06-22 18:35 ` Ivaylo Dimitrov
2016-06-23 9:16 ` Pavel Machek
2016-06-22 18:34 ` Ivaylo Dimitrov
2016-06-22 19:30 ` Ivaylo Dimitrov
2016-06-23 4:36 ` Tony Lindgren
2016-06-15 13:47 ` Sebastian Reichel
2016-06-15 18:34 ` Aaro Koskinen
2016-06-15 10:48 ` [PATCH 2/2] ARM: OMAP2+: Drop legacy board file for LDP Tony Lindgren
2016-08-05 17:45 ` [PATCH 0/2] Drop last two remaining omap3 legacy board files Sebastian Reichel
2016-08-06 6: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=20160615105552.GN29844@pali \
--to=pali.rohar@gmail.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).