On Thu, Oct 22, 2015 at 11:05:11AM +0200, Tomeu Vizoso wrote: > On 21 October 2015 at 23:50, Frank Rowand <frowand.l...@gmail.com> wrote: > > On 10/21/2015 2:12 PM, Rob Herring wrote: > >> On Wed, Oct 21, 2015 at 1:18 PM, Frank Rowand <frowand.l...@gmail.com> > >> wrote: > >>> On 10/21/2015 9:27 AM, Mark Brown wrote: > >>>> On Wed, Oct 21, 2015 at 08:59:51AM -0700, Frank Rowand wrote: > >>>>> On 10/19/2015 5:34 AM, Tomeu Vizoso wrote: > >>>> > >>>>>> To be clear, I was saying that this series should NOT affect total > >>>>>> boot times much. > >>>> > >>>>> I'm confused. If I understood correctly, improving boot time was > >>>>> the key justification for accepting this patch set. For example, > >>>>> from "[PATCH v7 0/20] On-demand device probing": > >>>>> > >>>>> I have a problem with the panel on my Tegra Chromebook taking longer > >>>>> than expected to be ready during boot (Stéphane Marchesin reported > >>>>> what > >>>>> is basically the same issue in [0]), and have looked into ordered > >>>>> probing as a better way of solving this than moving nodes around in > >>>>> the > >>>>> DT or playing with initcall levels and linking order. > >>>>> > >>>>> ... > >>>>> > >>>>> With this series I get the kernel to output to the panel in 0.5s, > >>>>> instead of 2.8s. > >>>> > >>>> Overall boot time and time to get some individual built in component up > >>>> and running aren't the same thing - what this'll do is get things up > >>>> more in the link order of the leaf consumers rather than deferring those > >>>> leaf consumers when their dependencies aren't ready yet. > >>> > >>> Thanks! I read too much into what was being improved. > >>> > >>> So this patch series, which on other merits may be a good idea, is as > >>> a by product solving a specific ordering issue, moving successful panel > >>> initialization to an earlier point in the boot sequence, if I now > >>> understand more correctly. > >>> > >>> In that context, this seems like yet another ad hoc way of causing the > >>> probe order to change in a way to solves one specific issue? Could > >>> it just as likely move the boot order of some other driver on some > >>> other board later, to the detriment of somebody else? > >> > >> Time to display on is important for many products. Having the console > >> up as early as possible is another case. CAN bus is another. This is a > >> real problem that is not just bad drivers. > > > > Yes, I agree. > > > > What I am seeing is that there continues to be a need for the ability > > to explicitly order at least some driver initialization (at some > > granularity), despite the push back against explicit ordering that > > has been present in the past. > > The important point that I have struggled to explain is that right now > for downstreams to influence the order in which devices are probed, > they have to carry a substantial amount of patches that cannot be ever > upstreamed. This fiddling with initcall levels and link order means > changing files that are very frequently changing, increasing the > amount of work when rebasing and increasing the probability of > regressions after a rebase. > > This just adds up to other shortcomings of mainline and ends up with > the net result of vendors getting stuck with 3.4 kernels on SoCs that > start production in 2015. Another consequence is that vendors don't > have a chance to upstream their stuff even if they cared. The > overarching goal of the project I'm in is to reduce those shortcomings > that downstreams have to workaround, to facilitate their involvement > upstream.
The init order of drivers has no influence at all on the ability for companies to have their individual drivers merged upstream, please don't be so dramatic about this. Worst case, a vendor keeps a single patch to drivers/Makefile in their tree that reorders things, yes it will get conflicts on every release, but really, it's trivial to maintain if they wish to keep doing this type of thing. Again, it is _not_ the reason that we are living with 2million+ lines of code in vendor kernels. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
