From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Possible Regression due to c074fef5d36e ("of/platform: Defer probes of registered devices").
Date: Mon, 26 Oct 2015 10:41:49 +0000 [thread overview]
Message-ID: <20151026104149.GB8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAMuHMdWmw8TqyOOMSPkh_1V+9OJeqPts1t3528ZQrJjzE6tmRA@mail.gmail.com>
On Mon, Oct 26, 2015 at 10:56:03AM +0100, Geert Uytterhoeven wrote:
> On Mon, Oct 26, 2015 at 10:40 AM, Sylvain Rochet
> <sylvain.rochet@finsecur.com> wrote:
> > On Mon, Oct 26, 2015 at 12:20:39PM +0900, Simon Horman wrote:
> >> I have observed a possible regression in next-20151022
> >> due to c074fef5d36e ("of/platform: Defer probes of registered devices").
> >>
> >> The problem manifests on the r8a7791 based koelsch board.
> >> With the above patch present booting the board using the shmobile_defconfig
> >> results in no console output. While after reverting the above patch
> >> the boot proceeds all the way to user-space.
> >>
> >> With DEBUG_LL and EARLY_PRINTK enabled I was able to capture some console
> >> output. I have included both that boot log, and a log of boot all the way to
> >> userspace with the patch in question reverted.
> >>
> >> The problem does not seem to manifiest on other boards for other
> >> Renesas ARM SoCs that I have access too. In particular the
> >> r8a7790 based lager board; the r8a7790 and r8a7791 are both members
> >> of the R-Car Gen2 family of SoCs.
> >
> > Atmel SoC hit this regresssion too, discussion about this issue is in
> > the following thread:
> > https://lkml.org/lkml/2015/10/16/733
>
> More reading material in "[GIT PULL] On-demand device probing"
> (https://lkml.org/lkml/2015/10/14/126)
It's quite obvious from the thread that the on-demand device probing is
*not* going to be merged for 4.4, and so it should not be in linux-next
at all. Having it in linux-next, it's disrupting people's testing of
the 4.4 merge window material.
Tomeu, please remove it so people can continue to test material
sheduled for the 4.4 merge window. Thanks.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-10-26 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 3:20 Possible Regression due to c074fef5d36e ("of/platform: Defer probes of registered devices") Simon Horman
2015-10-26 8:18 ` Geert Uytterhoeven
2015-10-26 9:40 ` Sylvain Rochet
2015-10-26 9:56 ` Geert Uytterhoeven
2015-10-26 10:41 ` Russell King - ARM Linux [this message]
2015-10-26 11:02 ` Geert Uytterhoeven
2015-10-26 12:47 ` Tomeu Vizoso
2015-10-26 13:23 ` Russell King - ARM Linux
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=20151026104149.GB8644@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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