Re: [PATCH v6 21/22] driver core: Start processing deferred probes earlier

From	Mark Brown <broonie@kernel.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH v6 21/22] driver core: Start processing deferred probes earlier
Date	2015-10-06 12:50 +0200
Message-ID	<qgxYK-3JK-5@gated-at.bofh.it> (permalink)
References	<qb9X3-rF-9@gated-at.bofh.it> <qb9X6-rF-71@gated-at.bofh.it> <qgnPI-5Rk-7@gated-at.bofh.it> <qgqDT-1vF-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Mon, Oct 05, 2015 at 09:49:38PM -0500, Rob Herring wrote:
> On Mon, Oct 5, 2015 at 6:52 PM, Frank Rowand <frowand.list@gmail.com> wrote:

> > The purpose of the *_sync initcall levels is to allow the corresponding
> > initcall level to use multiple threads of execution instead of a single
> > thread.  The *_sync level provides a location for a wait for all of the
> > threads at the corresponding init level to complete.  This is better
> > explained in the git log:

> The things I was worried about like clk and regulator disabling are
> actually late_initcall_sync, so maybe late_initcall is fine here after
> all.

> However, looking at other *_initcall_sync users, I'm not so sure they
> are doing the same abuse.

They're trying to run at the point where we've completed deferred
probe processing - in other words, at the sync point.  What they really
want is an additional callback at the point where the syncs have
actually happened.

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH v6 21/22] driver core: Start processing deferred probes  earlier Frank Rowand <frowand.list@gmail.com> - 2015-10-06 02:00 +0200
  Re: [PATCH v6 21/22] driver core: Start processing deferred probes earlier Rob Herring <robherring2@gmail.com> - 2015-10-06 05:00 +0200
    Re: [PATCH v6 21/22] driver core: Start processing deferred probes  earlier Mark Brown <broonie@kernel.org> - 2015-10-06 12:50 +0200

csiph-web