From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: mux: Use subsys_initcall for the i2c-arb-gpio-challenge
Date: Wed, 21 May 2014 12:26:53 +0200 [thread overview]
Message-ID: <20140521102653.GK2708@katana> (raw)
In-Reply-To: <1398351922-1647-1-git-send-email-ch.naveen@samsung.com>
On Thu, Apr 24, 2014 at 08:35:22PM +0530, Naveen Krishna Chatradhi wrote:
> From: Doug Anderson <dianders@chromium.org>
>
> Since many drivers rely on FETs that live behind this arbitrator, they
> can't successfully probe until after the arbitrator comes up. They
> ought to handle things properly with EPROBE_DEFER and still work, but
> that has some downsides:
>
> 1. Those drivers don't come up till later in the boot process. That
> really not so nice for the LCD--we want that to init early.
> 2. Some drivers have bugs and don't handle EPROBE_DEFER. Those
> drivers should be fixed but not all of them have been fixed yet.
> HDMI is one example since DRM doesn't really have good support for
> deferring probes.
>
> With this change We end up using the same init level as the main i2c bus.
>
> Signed-off-by: Doug Anderson <dianders@chromium.org>
> Reviewed-on: https://gerrit.chromium.org/gerrit/57007
> Reviewed-by: Simon Glass <sjg@chromium.org>
> Signed-off-by: Naveen Krishna Chatradhi <ch.naveen@samsung.com>
Same here. Unless we have a clear understanding that this is the only
acceptable solution in mainline, this is really an out-of-tree patch.
-------------- 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/20140521/ff8fe38a/attachment.sig>
prev parent reply other threads:[~2014-05-21 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 15:05 [PATCH] i2c: mux: Use subsys_initcall for the i2c-arb-gpio-challenge Naveen Krishna Chatradhi
2014-05-21 10:26 ` 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=20140521102653.GK2708@katana \
--to=wsa@the-dreams.de \
--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).