Re: [PATCH] drm: omap: fix: Defer probe if an omapdss device requests for it at connect

2013-09-20 Thread Tomi Valkeinen
On 18/09/13 14:08, Archit Taneja wrote: Some omapdss panels are connected to outputs/encoders(HDMI/DSI/DPI) that require regulators. The output's connect op tries to get a regulator which may not exist yet because it might get registered later in the kernel boot. omapdrm currently

Re: [PATCH] drm: omap: fix: Defer probe if an omapdss device requests for it at connect

2013-09-20 Thread Archit Taneja
On Friday 20 September 2013 01:39 PM, Tomi Valkeinen wrote: snip +static int omap_connect_dssdevs(void) +{ + int r; + struct omap_dss_device *dssdev = NULL; + + for_each_dss_dev(dssdev) { + r = dssdev-driver-connect(dssdev); + if (r ==

Re: [PATCH] drm: omap: fix: Defer probe if an omapdss device requests for it at connect

2013-09-20 Thread Tomi Valkeinen
On 20/09/13 11:49, Archit Taneja wrote: I suppose we would hit this case if all of the displays are deferred because of some dependency and are probed after omapdrm probes. Is that the case with beagle-xm? Yes, DVI is probed after omapdrm. There's also analog TV out on beagle. I'm not sure

Re: [PATCH] drm: omap: fix: Defer probe if an omapdss device requests for it at connect

2013-09-20 Thread Archit Taneja
On Friday 20 September 2013 02:25 PM, Tomi Valkeinen wrote: On 20/09/13 11:49, Archit Taneja wrote: I suppose we would hit this case if all of the displays are deferred because of some dependency and are probed after omapdrm probes. Is that the case with beagle-xm? Yes, DVI is probed after

Re: [PATCH] drm: omap: fix: Defer probe if an omapdss device requests for it at connect

2013-09-20 Thread Tomi Valkeinen
On 20/09/13 13:18, Archit Taneja wrote: On Friday 20 September 2013 02:25 PM, Tomi Valkeinen wrote: On 20/09/13 11:49, Archit Taneja wrote: I suppose we would hit this case if all of the displays are deferred because of some dependency and are probed after omapdrm probes. Is that the case

[PATCH] drm: omap: fix: Defer probe if an omapdss device requests for it at connect

2013-09-18 Thread Archit Taneja
Some omapdss panels are connected to outputs/encoders(HDMI/DSI/DPI) that require regulators. The output's connect op tries to get a regulator which may not exist yet because it might get registered later in the kernel boot. omapdrm currently ignores those panels which return a non zero value when

Re: [PATCH] drm: omap: fix: Defer probe if an omapdss device requests for it at connect

2013-09-18 Thread Archit Taneja
On Wednesday 18 September 2013 04:38 PM, Archit Taneja wrote: Some omapdss panels are connected to outputs/encoders(HDMI/DSI/DPI) that require regulators. The output's connect op tries to get a regulator which may not exist yet because it might get registered later in the kernel boot. omapdrm

Re: [PATCH] drm: omap: fix: Defer probe if an omapdss device requests for it at connect

2013-09-18 Thread Tomi Valkeinen
On 18/09/13 14:08, Archit Taneja wrote: Some omapdss panels are connected to outputs/encoders(HDMI/DSI/DPI) that require regulators. The output's connect op tries to get a regulator which may not exist yet because it might get registered later in the kernel boot. omapdrm currently

Re: [PATCH] drm: omap: fix: Defer probe if an omapdss device requests for it at connect

2013-09-18 Thread Archit Taneja
On Wednesday 18 September 2013 06:11 PM, Tomi Valkeinen wrote: On 18/09/13 14:08, Archit Taneja wrote: Some omapdss panels are connected to outputs/encoders(HDMI/DSI/DPI) that require regulators. The output's connect op tries to get a regulator which may not exist yet because it might get

Re: [PATCH] drm: omap: fix: Defer probe if an omapdss device requests for it at connect

2013-09-18 Thread Tomi Valkeinen
On 18/09/13 16:17, Archit Taneja wrote: On Wednesday 18 September 2013 06:11 PM, Tomi Valkeinen wrote: On 18/09/13 14:08, Archit Taneja wrote: Some omapdss panels are connected to outputs/encoders(HDMI/DSI/DPI) that require regulators. The output's connect op tries to get a regulator which