From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"myungjoo.ham@samsung.com" <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [RESEND PATCH v2 1/2] MFD: MAX77693: add MAX77693 MFD driver
Date: Sun, 13 May 2012 11:07:04 +0100 [thread overview]
Message-ID: <20120513100703.GA706@sirena.org.uk> (raw)
In-Reply-To: <20120511141508.GQ1214@sortiz-mobl>
On Fri, May 11, 2012 at 04:15:08PM +0200, Samuel Ortiz wrote:
> On Tue, Mar 20, 2012 at 10:07:58AM +0900, Chanwoo Choi wrote:
> > +static int __init max77693_i2c_init(void)
> > +{
> > + return i2c_add_driver(&max77693_i2c_driver);
> > +}
> > +/* init early so consumer devices can complete system boot */
> > +subsys_initcall(max77693_i2c_init);
> > +
> > +static void __exit max77693_i2c_exit(void)
> > +{
> > + i2c_del_driver(&max77693_i2c_driver);
> > +}
> > +module_exit(max77693_i2c_exit);
> You could use module_i2c_driver() here.
That doesn't work so well for PMICs yet - since cpufreq still doesn't
use struct device it can't use -EPROBE_DEFER which means that we need
the regulators to register before the cpufreq drivers and currently
we're doing that with the subsys_initcall() hack. Once cpufreq can
defer probes we should be able to stop doing this, it's the only blocker
at the minute.
next prev parent reply other threads:[~2012-05-13 10:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 5:28 [RESEND PATCH " Chanwoo Choi
2012-03-13 5:35 ` Venu Byravarasu
2012-03-13 5:39 ` Kyungmin Park
2012-03-13 5:52 ` Venu Byravarasu
2012-03-13 7:12 ` Chanwoo Choi
2012-03-13 7:19 ` Venu Byravarasu
2012-03-14 17:21 ` Mark Brown
2012-03-15 10:13 ` Chanwoo Choi
2012-03-20 1:07 ` [RESEND PATCH v2 " Chanwoo Choi
2012-05-11 14:15 ` Samuel Ortiz
2012-05-11 14:25 ` Kyungmin Park
2012-05-11 14:28 ` Kyungmin Park
2012-05-13 10:07 ` Mark Brown [this message]
2012-05-14 5:04 ` Chanwoo Choi
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=20120513100703.GA706@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sameo@linux.intel.com \
/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
all inboxes | Powered by JetHome®