From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: Tegra board file deprecation schedule Date: Fri, 27 Apr 2012 16:20:04 -0600 Message-ID: <4F9B1B94.2030909@wwwdotorg.org> References: <4F9B0E7C.1060408@wwwdotorg.org> <4F9B1568.9070704@wwwdotorg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Fabio Estevam Cc: Olof Johansson , "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Marc Dietrich , Thierry Reding , ARM kernel mailing list , Colin Cross List-Id: linux-tegra@vger.kernel.org On 04/27/2012 04:00 PM, Fabio Estevam wrote: > On Fri, Apr 27, 2012 at 6:53 PM, Stephen Warren wrote: > >> The only one sticking point might be that the Harmony regulator >> initialization needs to wait for the regulator driver to be probed, but >> happen before the PCIe driver is registers. Perhaps we could hook up >> some temporary bus notifiers to handle that. But since PCIe will likely >> be fixed in 3.6, we could probably just wait for that on Harmony. > > Does EPROBE_DEFER help in this case? That's certainly the solution when everything is instantiated from device tree, but I'm not sure it'll solve everything when doing the regulator stuff from temporary code in the board file, which won't be part of a driver probe.