From: Javier Martinez Canillas <martinez.javier@gmail.com> To: Tomi Valkeinen <tomi.valkeinen@ti.com>, Enric Balletbo Serra <eballetbo@gmail.com> Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>, Tony Lindgren <tony@atomide.com>, arm@kernel.org, "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH 1/6] ARM: OMAP2+: Remove board-4430sdp.c Date: Sun, 27 Oct 2013 14:26:31 +0100 [thread overview] Message-ID: <CAAwP0s2pGM6RRhkzhZ+_8BsCKP0posFrn7buTwUzLWWC5apE2A@mail.gmail.com> (raw) In-Reply-To: <51ECFDFD.60102@ti.com> Hi Tomi, On Mon, Jul 22, 2013 at 11:40 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote: > On 08/07/13 17:21, Russell King - ARM Linux wrote: > >> Also looks like the nonfunctional video stuff is even more nonfunctional >> than usual: >> >> omapdss DSI error: can't get VDDS_DSI regulator >> omapdss HDMI error: can't get VDDA_HDMI_DAC regulator I have the same issue when trying to get VDI output working on a IGEPv2 board. > > Those should be followed by "...requests probe deferral", and the driver > is probed again later. > When booting with DT the omapfb's probe is deferred several times but it always fails on dpi_connect() due not being able to get the VDDS_DSI regulator: [ 3.186035] OMAPFB: omapfb_probe [ 3.190704] omapdss DPI error: can't get VDDS_DSI regulator [ 3.196594] omapfb omapfb: failed to connect default display [ 3.202667] omapfb omapfb: failed to init overlay connections [ 3.208892] OMAPFB: free_resources [ 3.212493] OMAPFB: free all fbmem [ 3.216735] omapfb omapfb: failed to setup omapfb [ 3.221832] platform omapfb: Driver omapfb requests probe deferral [ 3.231689] OMAPFB: omapfb_probe [ 3.236175] omapdss DPI error: can't get VDDS_DSI regulator [ 3.242248] omapfb omapfb: failed to connect default display [ 3.248291] omapfb omapfb: failed to init overlay connections [ 3.254394] OMAPFB: free_resources [ 3.258026] OMAPFB: free all fbmem [ 3.262268] omapfb omapfb: failed to setup omapfb [ 3.267303] platform omapfb: Driver omapfb requests probe deferral My complete boot log is [1] I tracked down to dpi_init_regulator in drivers/video/omap2/dss/dpi.c static int dpi_init_regulator(void) { .... vdds_dsi = devm_regulator_get(&dpi.pdev->dev, "vdds_dsi"); if (IS_ERR(vdds_dsi)) { DSSERR("can't get VDDS_DSI regulator\n"); return PTR_ERR(vdds_dsi); } .... } So I tried adding this to my DT with no luck. diff --git a/arch/arm/boot/dts/omap3-igep0020.dts b/arch/arm/boot/dts/omap3-igep0020.dts index 17a6fc1..eaae935 100644 --- a/arch/arm/boot/dts/omap3-igep0020.dts +++ b/arch/arm/boot/dts/omap3-igep0020.dts @@ -256,3 +256,8 @@ &usbhsehci { phys = <&hsusb1_phy>; }; + +&vpll2 { + supply-dev = "omapdss_dpi.0"; + supply = "vdds_dsi"; +}; Now what you said does indeed happen when booting with the legacy board file. omapfb fails the first time with "can't get VDDS_DSI regulator" but the driver is probed again and it succeeds. I tried to spot a difference but didn't find it... > The log > http://www.arm.linux.org.uk/developer/build/result.php?type=boot&idx=946 > shows "taal display2: panel revision e3.83.7d" which hints that the > panel (and DSS) was initialized properly. > > Those error prints should probably be tuned down a bit now that the > driver uses probe deferral. > > Tomi > > fwiw, my wip branch is [2]: Javier Martinez Canillas (3): ARM: dts: omap3-igep0020: Add pinmux setup for i2c devices ARM: dts: omap3-igep0020: Add pinmuxig for DVI output ARM: OMAP: dss-common: change IGEP's DVI DDC i2c bus Any hints will be highly appreciated. Thanks a lot and best regards, Javier [1]: http://fpaste.org/49736/79384138/raw/ [2]: https://github.com/martinezjavier/linux/commits/igep-video-wip
WARNING: multiple messages have this Message-ID (diff)
From: martinez.javier@gmail.com (Javier Martinez Canillas) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/6] ARM: OMAP2+: Remove board-4430sdp.c Date: Sun, 27 Oct 2013 14:26:31 +0100 [thread overview] Message-ID: <CAAwP0s2pGM6RRhkzhZ+_8BsCKP0posFrn7buTwUzLWWC5apE2A@mail.gmail.com> (raw) In-Reply-To: <51ECFDFD.60102@ti.com> Hi Tomi, On Mon, Jul 22, 2013 at 11:40 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote: > On 08/07/13 17:21, Russell King - ARM Linux wrote: > >> Also looks like the nonfunctional video stuff is even more nonfunctional >> than usual: >> >> omapdss DSI error: can't get VDDS_DSI regulator >> omapdss HDMI error: can't get VDDA_HDMI_DAC regulator I have the same issue when trying to get VDI output working on a IGEPv2 board. > > Those should be followed by "...requests probe deferral", and the driver > is probed again later. > When booting with DT the omapfb's probe is deferred several times but it always fails on dpi_connect() due not being able to get the VDDS_DSI regulator: [ 3.186035] OMAPFB: omapfb_probe [ 3.190704] omapdss DPI error: can't get VDDS_DSI regulator [ 3.196594] omapfb omapfb: failed to connect default display [ 3.202667] omapfb omapfb: failed to init overlay connections [ 3.208892] OMAPFB: free_resources [ 3.212493] OMAPFB: free all fbmem [ 3.216735] omapfb omapfb: failed to setup omapfb [ 3.221832] platform omapfb: Driver omapfb requests probe deferral [ 3.231689] OMAPFB: omapfb_probe [ 3.236175] omapdss DPI error: can't get VDDS_DSI regulator [ 3.242248] omapfb omapfb: failed to connect default display [ 3.248291] omapfb omapfb: failed to init overlay connections [ 3.254394] OMAPFB: free_resources [ 3.258026] OMAPFB: free all fbmem [ 3.262268] omapfb omapfb: failed to setup omapfb [ 3.267303] platform omapfb: Driver omapfb requests probe deferral My complete boot log is [1] I tracked down to dpi_init_regulator in drivers/video/omap2/dss/dpi.c static int dpi_init_regulator(void) { .... vdds_dsi = devm_regulator_get(&dpi.pdev->dev, "vdds_dsi"); if (IS_ERR(vdds_dsi)) { DSSERR("can't get VDDS_DSI regulator\n"); return PTR_ERR(vdds_dsi); } .... } So I tried adding this to my DT with no luck. diff --git a/arch/arm/boot/dts/omap3-igep0020.dts b/arch/arm/boot/dts/omap3-igep0020.dts index 17a6fc1..eaae935 100644 --- a/arch/arm/boot/dts/omap3-igep0020.dts +++ b/arch/arm/boot/dts/omap3-igep0020.dts @@ -256,3 +256,8 @@ &usbhsehci { phys = <&hsusb1_phy>; }; + +&vpll2 { + supply-dev = "omapdss_dpi.0"; + supply = "vdds_dsi"; +}; Now what you said does indeed happen when booting with the legacy board file. omapfb fails the first time with "can't get VDDS_DSI regulator" but the driver is probed again and it succeeds. I tried to spot a difference but didn't find it... > The log > http://www.arm.linux.org.uk/developer/build/result.php?type=boot&idx=946 > shows "taal display2: panel revision e3.83.7d" which hints that the > panel (and DSS) was initialized properly. > > Those error prints should probably be tuned down a bit now that the > driver uses probe deferral. > > Tomi > > fwiw, my wip branch is [2]: Javier Martinez Canillas (3): ARM: dts: omap3-igep0020: Add pinmux setup for i2c devices ARM: dts: omap3-igep0020: Add pinmuxig for DVI output ARM: OMAP: dss-common: change IGEP's DVI DDC i2c bus Any hints will be highly appreciated. Thanks a lot and best regards, Javier [1]: http://fpaste.org/49736/79384138/raw/ [2]: https://github.com/martinezjavier/linux/commits/igep-video-wip
next prev parent reply other threads:[~2013-10-27 13:26 UTC|newest] Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-17 19:17 [PATCH 0/6] Drop legacy booting for omap4 for v3.11, boot with device tree only Tony Lindgren 2013-05-17 19:17 ` Tony Lindgren 2013-05-17 19:17 ` [PATCH 1/6] ARM: OMAP2+: Remove board-4430sdp.c Tony Lindgren 2013-05-17 19:17 ` Tony Lindgren 2013-05-20 9:54 ` Russell King - ARM Linux 2013-05-20 9:54 ` Russell King - ARM Linux 2013-05-20 17:10 ` Tony Lindgren 2013-05-20 17:10 ` Tony Lindgren 2013-07-06 13:10 ` Russell King - ARM Linux 2013-07-06 13:10 ` Russell King - ARM Linux 2013-07-06 13:36 ` Russell King - ARM Linux 2013-07-06 13:36 ` Russell King - ARM Linux 2013-07-08 9:34 ` Tony Lindgren 2013-07-08 9:34 ` Tony Lindgren 2013-07-08 14:21 ` Russell King - ARM Linux 2013-07-08 14:21 ` Russell King - ARM Linux 2013-07-09 8:23 ` Tony Lindgren 2013-07-09 8:23 ` Tony Lindgren 2013-07-12 9:09 ` Peter Ujfalusi 2013-07-12 9:09 ` Peter Ujfalusi 2013-07-22 9:40 ` Tomi Valkeinen 2013-07-22 9:40 ` Tomi Valkeinen 2013-10-27 13:26 ` Javier Martinez Canillas [this message] 2013-10-27 13:26 ` Javier Martinez Canillas 2013-10-28 13:32 ` Tomi Valkeinen 2013-10-28 13:32 ` Tomi Valkeinen 2013-10-28 14:25 ` Javier Martinez Canillas 2013-10-28 14:25 ` Javier Martinez Canillas 2013-07-13 2:31 ` Olof Johansson 2013-07-13 2:31 ` Olof Johansson 2013-07-13 3:10 ` Olof Johansson 2013-07-13 3:10 ` Olof Johansson 2013-07-15 6:55 ` Tony Lindgren 2013-07-15 6:55 ` Tony Lindgren 2013-07-06 21:36 ` Arnd Bergmann 2013-07-06 21:36 ` Arnd Bergmann 2013-07-06 23:37 ` debugging options (was: Re: [PATCH 1/6] ARM: OMAP2+: Remove board-4430sdp.c) Russell King - ARM Linux 2013-07-06 23:37 ` Russell King - ARM Linux 2013-05-17 19:17 ` [PATCH 2/6] ARM: OMAP2+: Remove board-omap4panda.c Tony Lindgren 2013-05-17 19:17 ` Tony Lindgren 2013-06-03 15:28 ` Ming Lei 2013-06-03 15:28 ` Ming Lei 2013-06-12 16:31 ` Tony Lindgren 2013-06-12 16:31 ` Tony Lindgren 2013-06-12 17:14 ` Tony Lindgren 2013-06-12 17:14 ` Tony Lindgren 2013-06-13 9:21 ` Sricharan R 2013-06-13 9:21 ` Sricharan R 2013-06-13 10:12 ` Sricharan R 2013-06-13 10:12 ` Sricharan R 2013-06-13 11:05 ` Tony Lindgren 2013-06-13 11:05 ` Tony Lindgren 2013-06-13 13:36 ` Ming Lei 2013-06-13 13:36 ` Ming Lei 2013-06-14 13:31 ` Ming Lei 2013-06-14 13:31 ` Ming Lei 2013-06-14 13:58 ` Ming Lei 2013-06-14 13:58 ` Ming Lei 2013-06-17 7:42 ` Sricharan R 2013-06-17 7:42 ` Sricharan R 2013-06-17 8:06 ` Arnaud Patard 2013-06-17 8:06 ` Arnaud Patard (Rtp) 2013-06-17 8:16 ` Ming Lei 2013-06-17 8:16 ` Ming Lei 2013-06-17 8:27 ` Tony Lindgren 2013-06-17 8:27 ` Tony Lindgren 2013-06-17 8:41 ` Ming Lei 2013-06-17 8:41 ` Ming Lei 2013-06-17 8:49 ` Tony Lindgren 2013-06-17 8:49 ` Tony Lindgren 2013-06-17 8:24 ` Tony Lindgren 2013-06-17 8:24 ` Tony Lindgren 2013-06-17 9:46 ` Arnaud Patard 2013-06-17 9:46 ` Arnaud Patard (Rtp) 2013-06-17 10:26 ` Tony Lindgren 2013-06-17 10:26 ` Tony Lindgren 2013-06-18 11:27 ` Tony Lindgren 2013-06-18 11:27 ` Tony Lindgren 2013-06-19 9:45 ` Arnaud Patard 2013-06-19 9:45 ` Arnaud Patard (Rtp) 2013-06-19 9:58 ` Tony Lindgren 2013-06-19 9:58 ` Tony Lindgren 2013-06-20 7:29 ` Arnaud Patard 2013-06-20 7:29 ` Arnaud Patard (Rtp) 2013-06-21 6:01 ` Tony Lindgren 2013-06-21 6:01 ` Tony Lindgren 2013-05-17 19:17 ` [PATCH 3/6] ARM: OMAP2+: Remove legacy mux data for omap4 Tony Lindgren 2013-05-17 19:17 ` Tony Lindgren 2013-05-17 19:17 ` [PATCH 4/6] ARM: OMAP2+: Remove omap4 pdata from hsmmc.c Tony Lindgren 2013-05-17 19:17 ` Tony Lindgren 2013-05-17 19:18 ` [PATCH 5/6] ARM: OMAP2+: Remove omap4 pdata for USB Tony Lindgren 2013-05-17 19:18 ` Tony Lindgren 2013-05-17 19:18 ` [PATCH 6/6] ARM: OMAP2+: Remove omap4 ocp2scp pdata Tony Lindgren 2013-05-17 19:18 ` Tony Lindgren 2013-05-17 20:05 ` Felipe Balbi 2013-05-17 20:05 ` Felipe Balbi 2013-05-21 11:53 ` Kishon Vijay Abraham I 2013-05-21 11:53 ` Kishon Vijay Abraham I 2013-06-07 10:05 ` [PATCH 0/6] Drop legacy booting for omap4 for v3.11, boot with device tree only Tomi Valkeinen 2013-06-07 10:05 ` Tomi Valkeinen
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=CAAwP0s2pGM6RRhkzhZ+_8BsCKP0posFrn7buTwUzLWWC5apE2A@mail.gmail.com \ --to=martinez.javier@gmail.com \ --cc=arm@kernel.org \ --cc=eballetbo@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=tomi.valkeinen@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.