From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: sirf: move driver init from module_init to subsys_initcall
Date: Mon, 27 May 2013 08:16:58 -0400 [thread overview]
Message-ID: <20130527121658.GA3660@sirena.org.uk> (raw)
In-Reply-To: <CAGsJ_4y6SY6nNkbW+Yh8jx0WB4Pi9MO1W3xVZcrQcedGeD5ogQ@mail.gmail.com>
On Mon, May 27, 2013 at 09:54:56AM +0800, Barry Song wrote:
> Mark, the case is not that deferred probing is slow or not. deferred
> probing is pretty good.
> the case is that we want to i2c and media connected with i2c probed
> earlier than other devices.
> in auto infotainment devices, we actually do some hacking in kernel
> that makes rear view work earlier than other device driver
> initialization with a kernel thread which take care of backing-car
> policy not only mechanism. that means, we make camera work to see
> backview image even earlier than other drivers' initialization.
> we don't want media deferred to wait for i2c. we want make some early
> jobs ready earlier.
So this change makes no practical difference in mainline and exists to
support out of tree hacks for performance? It doesn't seem like that
big a patch to carry along with the out of tree stuff...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130527/ecbd0662/attachment.sig>
next prev parent reply other threads:[~2013-05-27 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 2:50 [PATCH] i2c: sirf: move driver init from module_init to subsys_initcall Barry Song
2013-05-16 9:38 ` Wolfram Sang
2013-05-16 10:25 ` Barry Song
2013-05-25 20:10 ` Mark Brown
2013-05-27 1:54 ` Barry Song
2013-05-27 12:16 ` Mark Brown [this message]
2013-05-27 15:36 ` Barry Song
2013-06-10 13:45 ` Wolfram Sang
2013-06-11 1:14 ` Barry Song
2013-06-11 8:48 ` Mark Brown
2013-06-11 11:13 ` Barry Song
2013-06-11 12:10 ` Mark Brown
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=20130527121658.GA3660@sirena.org.uk \
--to=broonie@kernel.org \
--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).