linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sre@ring0.de>
Cc: Nishanth Menon <nm@ti.com>, Aaro Koskinen <aaro.koskinen@iki.fi>,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
Date: Wed, 29 Oct 2014 12:39:16 -0700	[thread overview]
Message-ID: <20141029193915.GB2542@atomide.com> (raw)
In-Reply-To: <20141029185957.GA3723@earth.universe>

* Sebastian Reichel <sre@ring0.de> [141029 12:01]:
> Hi,
> 
> On Wed, Oct 29, 2014 at 08:43:03AM -0500, Nishanth Menon wrote:
> > On 10/28/2014 05:12 PM, Tony Lindgren wrote:
> > > * Aaro Koskinen <aaro.koskinen@iki.fi> [141027 16:03]:
> > >> Hi,
> > >>
> > >> On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
> > >>> +
> > >>> +	if (!of_have_populated_dt())
> > >>> +		pr_warn("WARNING: legacy booting deprecated, please update to boot with .dts\n");
> > >>> +
> > >>
> > >> Maybe use WARN so that the warning is more verbose and kernel gets tainted?
> > > 
> > > Well I was hoping to avoid annoying people with the trace.
> > > But can do that if people prefer that, what do others think?
> > > 
> > 
> > WARN is better and eye catchy. Also, could we add information on when
> > the support will be removed since we call it deprecated?

Well quoting the hostage situation from a Mr. Show episode
"Now Who Wants Ice Cream?" the answer to that would be:

OK, you want me to guess? A hundred million days, or maybe ten more
minutes, somewhere in there, I just can't say, don't know.
 
> I also think, that more eye catchy is better.

OK, updated patch below. I'd like to add this to the current
-rc cycle unless people have objections to that.
 
> Apart from that I wonder if we should drop support on a
> board-by-board basis and then drop omap3 support completly once all
> boards have been dropped.

Yes. I'll post few patches from my old board removal branch at
omap-for-v3.14/omap3-board-removal shortly.

Regards,

Tony

8< -----------------------
From: Tony Lindgren <tony@atomide.com>
Date: Mon, 27 Oct 2014 13:05:54 -0700
Subject: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode

We're moving omaps to use device tree based booting and already have
omap2, omap4, omap5, am335x and am437x booting in device tree only
mode.

Only omap3 still has legacy booting still around and we really want
to make that device tree only. So let's add a warning about deprecated
legacy booting so we get people to upgrade their boards to use device
tree based booting and find out about any remaining issues.

Note that for most boards we already have the .dts file and those can
be booted with without changing the bootloader using the appended
DTB mode.

Signed-off-by: Tony Lindgren <tony@atomide.com>

--- a/arch/arm/mach-omap2/omap_device.c
+++ b/arch/arm/mach-omap2/omap_device.c
@@ -917,6 +917,10 @@ static int __init omap_device_late_idle(struct device *dev, void *data)
 static int __init omap_device_late_init(void)
 {
 	bus_for_each_dev(&platform_bus_type, NULL, NULL, omap_device_late_idle);
+
+	WARN(!of_have_populated_dt(),
+		"legacy booting deprecated, please update to boot with .dts\n");
+
 	return 0;
 }
 omap_late_initcall_sync(omap_device_late_init);

  reply	other threads:[~2014-10-29 19:40 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 20:00 [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode Tony Lindgren
2014-10-27 23:01 ` Aaro Koskinen
2014-10-28 22:12   ` Tony Lindgren
2014-10-29 13:43     ` Nishanth Menon
2014-10-29 18:59       ` Sebastian Reichel
2014-10-29 19:39         ` Tony Lindgren [this message]
2014-10-29 21:45           ` Nishanth Menon
2014-10-29 22:15             ` Tony Lindgren
2014-10-29 22:31             ` Aaro Koskinen
2014-10-30 13:55               ` Nishanth Menon
2014-10-29 23:07           ` Sebastian Reichel
2014-10-29 23:11           ` Aaro Koskinen
2014-10-29 23:54             ` Javier Martinez Canillas
2014-11-26 17:28   ` Pavel Machek
2014-11-26 18:19     ` Tony Lindgren
2014-11-26 18:57       ` Pali Rohár
2014-11-26 19:10         ` Tony Lindgren
2014-11-26 19:22           ` Pali Rohár
2014-11-26 20:08             ` Tony Lindgren
2014-11-26 23:01               ` Pali Rohár
2014-11-26 23:14                 ` Tony Lindgren
2014-11-26 23:38                   ` Pali Rohár
2014-11-27  1:12                     ` Tony Lindgren
2014-11-27 11:32                       ` Pali Rohár
2014-11-28 20:27                         ` Tony Lindgren
2014-11-28 21:41                           ` Pali Rohár
2014-11-28 22:24                             ` Tony Lindgren
2014-11-28 22:42                               ` Pali Rohár
2014-12-04 18:34                               ` Pali Rohár
2014-12-04 18:40                                 ` Tony Lindgren
2014-12-04 19:01                                   ` Pali Rohár
2014-11-28 22:26                             ` Aaro Koskinen
2014-11-28 22:43                               ` Pali Rohár
2014-11-28 22:41                             ` Aaro Koskinen
2014-11-28 22:49                               ` Pali Rohár
2014-11-28 22:54                                 ` Aaro Koskinen
2014-12-02 21:28                           ` Pali Rohár
2014-12-03 16:52                           ` Pavel Machek
2014-12-03 22:22                             ` Dmitry Eremin-Solenikov
2014-11-27 11:18               ` Pavel Machek
2014-10-31 19:30 ` Russell King - ARM Linux
2014-10-31 21:13   ` Tony Lindgren
2014-10-31 22:12     ` Tony Lindgren
2014-10-31 22:33     ` Russell King - ARM Linux
2014-10-31 23:37       ` Tony Lindgren
2014-11-01  0:44         ` Russell King - ARM Linux
2014-11-01 21:57           ` Tony Lindgren
2014-11-02 18:15             ` 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=20141029193915.GB2542@atomide.com \
    --to=tony@atomide.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=sre@ring0.de \
    /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).