From: tomi.valkeinen@ti•com (Tomi Valkeinen)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/6] ARM: OMAP2+: Remove board-4430sdp.c
Date: Mon, 28 Oct 2013 15:32:21 +0200 [thread overview]
Message-ID: <526E6765.3030403@ti.com> (raw)
In-Reply-To: <CAAwP0s2pGM6RRhkzhZ+_8BsCKP0posFrn7buTwUzLWWC5apE2A@mail.gmail.com>
On 27/10/13 15:26, Javier Martinez Canillas wrote:
> 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:
The problem with DT boot is that the VDDS_DSI is not linked to the DPI
device. For omap4, we have a few hacks to go around this (see dsi.c,
dsi_regulator_init()).
> 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";
> +};
I didn't see "supply-dev" defined in dt bindings documentation, is that
supposed to work? If it should work, then the problem could be solved
with the above. Otherwise I guess we must add more hacks to omapdss
driver, to all places where it uses regulator_get...
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131028/a76b34f1/attachment.sig>
next prev parent reply other threads:[~2013-10-28 13:32 UTC|newest]
Thread overview: 50+ 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 ` [PATCH 1/6] ARM: OMAP2+: Remove board-4430sdp.c Tony Lindgren
2013-05-20 9:54 ` Russell King - ARM Linux
2013-05-20 17:10 ` Tony Lindgren
2013-07-06 13:10 ` Russell King - ARM Linux
2013-07-06 13:36 ` Russell King - ARM Linux
2013-07-08 9:34 ` Tony Lindgren
2013-07-08 14:21 ` Russell King - ARM Linux
2013-07-09 8:23 ` Tony Lindgren
2013-07-12 9:09 ` Peter Ujfalusi
2013-07-22 9:40 ` Tomi Valkeinen
2013-10-27 13:26 ` Javier Martinez Canillas
2013-10-28 13:32 ` Tomi Valkeinen [this message]
2013-10-28 14:25 ` Javier Martinez Canillas
2013-07-13 2:31 ` Olof Johansson
2013-07-13 3:10 ` Olof Johansson
2013-07-15 6:55 ` Tony Lindgren
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-05-17 19:17 ` [PATCH 2/6] ARM: OMAP2+: Remove board-omap4panda.c Tony Lindgren
2013-06-03 15:28 ` Ming Lei
2013-06-12 16:31 ` Tony Lindgren
2013-06-12 17:14 ` Tony Lindgren
2013-06-13 9:21 ` Sricharan R
2013-06-13 10:12 ` Sricharan R
2013-06-13 11:05 ` Tony Lindgren
2013-06-13 13:36 ` Ming Lei
2013-06-14 13:31 ` Ming Lei
2013-06-14 13:58 ` Ming Lei
2013-06-17 7:42 ` Sricharan R
2013-06-17 8:06 ` Arnaud Patard (Rtp)
2013-06-17 8:16 ` Ming Lei
2013-06-17 8:27 ` Tony Lindgren
2013-06-17 8:41 ` Ming Lei
2013-06-17 8:49 ` Tony Lindgren
2013-06-17 8:24 ` Tony Lindgren
2013-06-17 9:46 ` Arnaud Patard (Rtp)
2013-06-17 10:26 ` Tony Lindgren
2013-06-18 11:27 ` Tony Lindgren
2013-06-19 9:45 ` Arnaud Patard (Rtp)
2013-06-19 9:58 ` Tony Lindgren
2013-06-20 7:29 ` Arnaud Patard (Rtp)
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 ` [PATCH 4/6] ARM: OMAP2+: Remove omap4 pdata from hsmmc.c Tony Lindgren
2013-05-17 19:18 ` [PATCH 5/6] ARM: OMAP2+: Remove omap4 pdata for USB Tony Lindgren
2013-05-17 19:18 ` [PATCH 6/6] ARM: OMAP2+: Remove omap4 ocp2scp pdata Tony Lindgren
2013-05-17 20:05 ` Felipe Balbi
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
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=526E6765.3030403@ti.com \
--to=tomi.valkeinen@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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