From: Tushar Behera <tushar.behera@linaro.org>
To: Mark Brown <broonie@kernel.org>,
Naveen Krishna Chatradhi <ch.naveen@samsung.com>
Cc: linux-i2c@vger.kernel.org, naveenkrishna.ch@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, sjg@chromium.org,
grundler@chromium.org, linux-kernel@vger.kernel.org,
wsa@the-dreams.de, cpgs@samsung.com
Subject: Re: [PATCH] i2c: exynos5: Initialise Samsung High Speed I2C controller early
Date: Fri, 25 Apr 2014 10:28:06 +0530 [thread overview]
Message-ID: <5359EB5E.7010800@linaro.org> (raw)
In-Reply-To: <20140424162558.GB12304@sirena.org.uk>
On 04/24/2014 09:55 PM, Mark Brown wrote:
> On Thu, Apr 24, 2014 at 08:18:36PM +0530, Naveen Krishna Chatradhi wrote:
>> This patch moves initialization code to subsys_initcall() to ensure
>> that the i2c bus is available early so the regulators can be quickly
>> probed and available for other devices on their probe() call.
>
>> Such solution has been proposed by Mark Brown to fix the problem of
>> the regulators not beeing available on the peripheral device probe():
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/011971.html
>
> What specifically is this needed for? We *should* be able to use
> deferred probe for most things, but I know that not all subsystems are
> able to yet.
>
DRM-Exynos is one such sub-system right now that doesn't handle deferred
probe well. That is one of the reasons for this patch.
--
Tushar Behera
WARNING: multiple messages have this Message-ID (diff)
From: tushar.behera@linaro.org (Tushar Behera)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: exynos5: Initialise Samsung High Speed I2C controller early
Date: Fri, 25 Apr 2014 10:28:06 +0530 [thread overview]
Message-ID: <5359EB5E.7010800@linaro.org> (raw)
In-Reply-To: <20140424162558.GB12304@sirena.org.uk>
On 04/24/2014 09:55 PM, Mark Brown wrote:
> On Thu, Apr 24, 2014 at 08:18:36PM +0530, Naveen Krishna Chatradhi wrote:
>> This patch moves initialization code to subsys_initcall() to ensure
>> that the i2c bus is available early so the regulators can be quickly
>> probed and available for other devices on their probe() call.
>
>> Such solution has been proposed by Mark Brown to fix the problem of
>> the regulators not beeing available on the peripheral device probe():
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/011971.html
>
> What specifically is this needed for? We *should* be able to use
> deferred probe for most things, but I know that not all subsystems are
> able to yet.
>
DRM-Exynos is one such sub-system right now that doesn't handle deferred
probe well. That is one of the reasons for this patch.
--
Tushar Behera
next prev parent reply other threads:[~2014-04-25 4:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 14:48 [PATCH] i2c: exynos5: Initialise Samsung High Speed I2C controller early Naveen Krishna Chatradhi
2014-04-24 14:48 ` Naveen Krishna Chatradhi
2014-04-24 14:48 ` Naveen Krishna Chatradhi
2014-04-24 16:25 ` Mark Brown
2014-04-24 16:25 ` Mark Brown
2014-04-25 4:58 ` Tushar Behera [this message]
2014-04-25 4:58 ` Tushar Behera
[not found] ` <20140424162558.GB12304-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-05-09 12:20 ` Naveen Krishna Ch
2014-05-09 12:20 ` Naveen Krishna Ch
2014-05-09 12:20 ` Naveen Krishna Ch
2014-05-09 13:51 ` Mark Brown
2014-05-09 13:51 ` Mark Brown
[not found] ` <20140509135153.GM12304-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-05-09 14:42 ` Naveen Krishna Ch
2014-05-09 14:42 ` Naveen Krishna Ch
2014-05-09 14:42 ` Naveen Krishna Ch
[not found] ` <CAHfPSqDSTyQXPT-NCZ2hE01qpdmaR54tbWCUYC_zSDGFp58+7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-09 14:54 ` Mark Brown
2014-05-09 14:54 ` Mark Brown
2014-05-09 14:54 ` Mark Brown
2014-05-21 10:25 ` Wolfram Sang
2014-05-21 10:25 ` Wolfram Sang
2014-05-21 12:04 ` Naveen Krishna Ch
2014-05-21 12:04 ` Naveen Krishna Ch
[not found] ` <CAHfPSqCOnW4YGPfMfpBMbLSaiSxRN=CHJK6kYdkXMujKvNwAPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-21 13:00 ` Wolfram Sang
2014-05-21 13:00 ` Wolfram Sang
2014-05-21 13:00 ` Wolfram Sang
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=5359EB5E.7010800@linaro.org \
--to=tushar.behera@linaro.org \
--cc=broonie@kernel.org \
--cc=ch.naveen@samsung.com \
--cc=cpgs@samsung.com \
--cc=grundler@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=naveenkrishna.ch@gmail.com \
--cc=sjg@chromium.org \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.