From: Tony Lindgren <tony@atomide.com>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: Benoit Cousson <b-cousson@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Porter <mporter@ti.com>,
Koen Kooi <koen@dominion.thruhere.net>,
Shubhrajyoti D <shubhrajyoti@ti.com>
Subject: Re: [PATCH 1/3] pinctrl: pinctrl-single must be initialized early.
Date: Thu, 20 Sep 2012 17:09:22 -0700 [thread overview]
Message-ID: <20120921000922.GQ28835@atomide.com> (raw)
In-Reply-To: <B7D59159-4456-468B-A414-9B57BCEE018D@antoniou-consulting.com>
* Pantelis Antoniou <panto@antoniou-consulting.com> [120918 12:11]:
>
> As long as we get the regulator to work early in the game no problem.
> I don't know if deferring the probe will work in this case.
> I could give it a shot and see if it works at all.
Did you have any luck with deferred probe here?
Tony
next prev parent reply other threads:[~2012-09-21 0:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 16:07 [PATCH 0/3] Pinctrl-fy OMAP I2C driver Pantelis Antoniou
2012-09-19 16:07 ` [PATCH 1/3] pinctrl: pinctrl-single must be initialized early Pantelis Antoniou
2012-09-18 18:21 ` Tony Lindgren
2012-09-18 19:10 ` Pantelis Antoniou
2012-09-21 0:09 ` Tony Lindgren [this message]
2012-09-19 16:07 ` [PATCH 2/3] OMAP i2c: pinctrl-ify i2c-omap.c Pantelis Antoniou
2012-09-18 18:23 ` Tony Lindgren
2012-09-18 19:37 ` Pantelis Antoniou
2012-09-19 7:09 ` Shubhrajyoti
2012-09-19 8:34 ` Pantelis Antoniou
2012-09-20 6:34 ` [PATCH 0/2] Pinctrl-fy OMAP I2C driver (V2) Pantelis Antoniou
2012-09-20 6:34 ` [PATCH 1/2] pinctrl: pinctrl-single must be initialized early Pantelis Antoniou
2012-09-20 6:34 ` [PATCH 2/2] OMAP i2c: pinctrl-ify i2c-omap.c Pantelis Antoniou
2012-09-19 10:13 ` Shubhrajyoti Datta
2012-09-19 17:24 ` Tony Lindgren
2012-09-21 7:29 ` [PATCH 2/3] " Peter Ujfalusi
2012-09-21 7:34 ` Pantelis Antoniou
2012-09-19 16:07 ` [PATCH 3/3] i2c: OMAP fix driver initialization message Pantelis Antoniou
2012-09-18 18:24 ` Tony Lindgren
2012-09-18 19:24 ` a0919096
2012-09-19 9:57 ` Pantelis Antoniou
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=20120921000922.GQ28835@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mporter@ti.com \
--cc=panto@antoniou-consulting.com \
--cc=shubhrajyoti@ti.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;
as well as URLs for NNTP newsgroup(s).