linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@antoniou-consulting.com>
To: Tony Lindgren <tony@atomide.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: Tue, 18 Sep 2012 22:10:08 +0300	[thread overview]
Message-ID: <B7D59159-4456-468B-A414-9B57BCEE018D@antoniou-consulting.com> (raw)
In-Reply-To: <20120918182150.GY11762@atomide.com>

Hi Tony,

On Sep 18, 2012, at 9:21 PM, Tony Lindgren wrote:

> Hi,
> 
> * Pantelis Antoniou <panto@antoniou-consulting.com> [120918 11:13]:
>> When using pinctrl-single to handle i2c initialization, it has
>> to be done early.
>> On the beaglebone the regulator is connected to the i2c0 bus,
>> and for sure that's the case for many other am33xx boards.
> 
> Usually it's better to initialize things later than earlier as
> that cuts down nasty dependencies and let's us have a proper
> debug console before we start initializing things beyond
> interrupts and drivers.
> 

Agreed.

> Maybe just fix up the i2c-omap.c not to use subsys_initcall()?
> And then deferred probe should be able to sort out the dependencies
> for other drivers depending on i2c?
> 

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.

FWIW, the regulator is on I2C0 which doesn't need any pinmux setup.
So in theory I2C0 is ready to go without any pinctrl action, however
the other busses require it.

It's not clear how to do so without making the driver all hacky.
Perhaps a property that signals that no pinctrl binding is required.


> Regards,
> 
> Tony
> 

Regards

-- Pantelis

>> Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com>
>> ---
>> drivers/pinctrl/pinctrl-single.c | 12 +++++++++++-
>> 1 file changed, 11 insertions(+), 1 deletion(-)
>> 
>> diff --git a/drivers/pinctrl/pinctrl-single.c b/drivers/pinctrl/pinctrl-single.c
>> index 76a4260..3acf7f9 100644
>> --- a/drivers/pinctrl/pinctrl-single.c
>> +++ b/drivers/pinctrl/pinctrl-single.c
>> @@ -980,7 +980,17 @@ static struct platform_driver pcs_driver = {
>> 	},
>> };
>> 
>> -module_platform_driver(pcs_driver);
>> +static int __init pcs_init(void)
>> +{
>> +	return platform_driver_register(&pcs_driver);
>> +}
>> +postcore_initcall(pcs_init);
>> +
>> +static void __exit pcs_exit(void)
>> +{
>> +	platform_driver_unregister(&pcs_driver);
>> +}
>> +module_exit(pcs_exit);
>> 
>> MODULE_AUTHOR("Tony Lindgren <tony@atomide.com>");
>> MODULE_DESCRIPTION("One-register-per-pin type device tree based pinctrl driver");
>> -- 
>> 1.7.12
>> 


  reply	other threads:[~2012-09-18 19:10 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 [this message]
2012-09-21  0:09       ` Tony Lindgren
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=B7D59159-4456-468B-A414-9B57BCEE018D@antoniou-consulting.com \
    --to=panto@antoniou-consulting.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=shubhrajyoti@ti.com \
    --cc=tony@atomide.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).