From: Wolfram Sang <wsa@the-dreams.de>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: Walter Lozano <walter@vanguardiasur.com.ar>,
mika.westerberg@linux.intel.com, Romain.Baeriswyl@abilis.com,
atull@opensource.altera.com, raymond.tan@intel.com,
carlpeng008@gmail.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] i2c: designware: Avoid initcall and initialize the driver like a regular one
Date: Tue, 23 Dec 2014 17:23:58 +0100 [thread overview]
Message-ID: <20141223162357.GA4467@katana> (raw)
In-Reply-To: <54998B1A.9020208@vanguardiasur.com.ar>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
> >> This means there won't be any early users of the I2C platform driver in this
> >> scenario.
> >
> > There won't be with platform as well.
>
> Oh, OK. Then maybe you can clarify why all those i2c busses need to be
> registered with initcall in the first place?
Because they want to access PMICs early to have voltages ready when
other drivers are probed. This, again, is DT/platform independent.
All this is cruft from the pre-deferred-probe era. And pretty annoying
to deprecated although I'd love to do that.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-12-23 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 18:15 [RFC] i2c: designware: Avoid initcall and initialize the driver like a regular one Walter Lozano
2014-12-22 19:02 ` Wolfram Sang
2014-12-23 12:53 ` Walter Lozano
2014-12-23 14:57 ` Ezequiel Garcia
2014-12-23 15:26 ` Wolfram Sang
2014-12-23 15:32 ` Ezequiel Garcia
2014-12-23 16:23 ` Wolfram Sang [this message]
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=20141223162357.GA4467@katana \
--to=wsa@the-dreams.de \
--cc=Romain.Baeriswyl@abilis.com \
--cc=atull@opensource.altera.com \
--cc=carlpeng008@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=raymond.tan@intel.com \
--cc=walter@vanguardiasur.com.ar \
/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