linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Barry Song <Baohua.Song-kQvG35nSl+M@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	workgroup.linux-kQvG35nSl+M@public.gmane.org,
	Xiaomeng Hou <Xiaomeng.Hou-kQvG35nSl+M@public.gmane.org>
Subject: Re: [PATCH] i2c: sirf: move driver init from module_init to subsys_initcall
Date: Thu, 16 May 2013 11:38:49 +0200	[thread overview]
Message-ID: <20130516093846.GA2927@katana> (raw)
In-Reply-To: <1368672607-5536-1-git-send-email-Baohua.Song-kQvG35nSl+M@public.gmane.org>

On Thu, May 16, 2013 at 10:50:07AM +0800, Barry Song wrote:
> From: Xiaomeng Hou <Xiaomeng.Hou-kQvG35nSl+M@public.gmane.org>
> 
> if we initilize i2c bus by module_init, there are some devices which want
> initialization earlier than i2c and could not do that in time, so move i2c
> driver initilization to subsys_initcall and make i2c ready before devices
> init.
> 
> Signed-off-by: Xiaomeng Hou <Xiaomeng.Hou-kQvG35nSl+M@public.gmane.org>
> Signed-off-by: Barry Song <Baohua.Song-kQvG35nSl+M@public.gmane.org>

What about deferred probing?

  parent reply	other threads:[~2013-05-16  9:38 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
     [not found] ` <1368672607-5536-1-git-send-email-Baohua.Song-kQvG35nSl+M@public.gmane.org>
2013-05-16  9:38   ` Wolfram Sang [this message]
2013-05-16 10:25     ` Barry Song
     [not found]       ` <CAGsJ_4zVOF8-g=emEGgP3atxkWdxMaQQiVZrZkht_WueTriSnw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-25 20:10         ` Mark Brown
     [not found]           ` <20130525201032.GD32043-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-05-27  1:54             ` Barry Song
     [not found]               ` <CAGsJ_4y6SY6nNkbW+Yh8jx0WB4Pi9MO1W3xVZcrQcedGeD5ogQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-27 12:16                 ` Mark Brown
     [not found]                   ` <20130527121658.GA3660-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-05-27 15:36                     ` Barry Song
     [not found]                       ` <CAGsJ_4w867BhFvVze5BNaYheW75pMcOGhscz3wSZiia-neP59w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-10 13:45                         ` Wolfram Sang
2013-06-11  1:14                           ` Barry Song
     [not found]                             ` <CAGsJ_4y4svi0TbUKK1aAW1McM5rFoo5Vb9rGPweq-sHJ2NN5cQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-11  8:48                               ` Mark Brown
     [not found]                                 ` <20130611084827.GS1403-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-06-11 11:13                                   ` Barry Song
     [not found]                                     ` <CAGsJ_4wH=mNxBTqizKjJR2YhmVQa=iprfUmVYy8oz7MZeLfkqg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=20130516093846.GA2927@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=Baohua.Song-kQvG35nSl+M@public.gmane.org \
    --cc=Xiaomeng.Hou-kQvG35nSl+M@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=workgroup.linux-kQvG35nSl+M@public.gmane.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).