[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <96C9D994977DD0439FB6D3FE3B13DD907DBD3AA01F@BGMAIL01.nvidia.com>
Date: Fri, 6 Jan 2012 16:49:50 +0530
From: Laxman Dewangan <ldewangan@...dia.com>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC: Laxman Dewangan <ldewangan.com@...dia.com>,
"lrg@...mlogic.co.uk" <lrg@...mlogic.co.uk>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>
Subject: RE: [PATCH V1] regulator: fixed: Move drivers to
subsys_initcall_sync()
> From: linux-pm-owner@...r.kernel.org [mailto:linux-pm-owner@...r.kernel.org]
> On Behalf Of Mark Brown
> Sent: Friday, January 06, 2012 12:24 PM
> > is in subsys_initcall_sync() in place of arch_init, although driver is in
> > subsys_initcall() to postponed the probe calling.
>
> > What do you suggest on this case?
>
> Honestly I'd suggest that you contribute to the effort to get the probe
> ordering handling code implemented in mainline. This just seems like a
> big can of worms to open up for something that's hopefully just going to
> be a short term thing. It's a real problem but this seems fairly niche
> and like if we start doing more than we're already doing we're going to
> end up running around chasing our own tails on this stuff. I'm really
> not sure what the status is on that work, though - it may be that you
> actually need to pick the patches up and push them forwards yourself.
Completely agree with you. I went through the Grant's change
" drivercore: Add driver probe deferral mechanism" and it is
discussed in more details here. I will start different thread
communication on this issue.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists