All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Enric Balletbo i Serra <eballetbo@gmail.com>,
	bcousson@baylibre.com, tomi.valkeinen@ti.com,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 11/11] OMAPDSS: DPI: use VPLL2 regulator if VDDS_DSI is not found
Date: Sat, 16 Nov 2013 07:45:07 -0800	[thread overview]
Message-ID: <20131116154507.GL10317@atomide.com> (raw)
In-Reply-To: <5287908C.3040602@collabora.co.uk>

* Javier Martinez Canillas <javier.martinez@collabora.co.uk> [131116 07:36]:
> Hi Tony,
> 
> On 11/16/2013 03:18 PM, Tony Lindgren wrote:
> > * Javier Martinez Canillas <javier.martinez@collabora.co.uk> [131116 05:25]:
> >> On Device Tree boot the VDDS_DSI regulator is not linked to
> >> the DPI device so omapfb driver probing fails with:
> >> 
> >> [    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
> >> 
> >> As a workaround try to use the VPLL2 regulator from twl4030 in
> >> dpi_init_regulator() if getting the VDDS_DSI regulator fails.
> > 
> > Probably makes sens to fix this in the dpi.c, but this can also be set
> > in the .dts file. I just set up the following in the omap3-ldp.dts file:
> > 
> 
> Sorry is not clear to me if you agree that makes sense to do this fix on dpi.c
> or if you think this is a bad idea and prefer to do it in the DTS instead?
> 
> I'm asking to know if I have to send a follow up patch or not :)

Well let's see what Tomi prefers.

> > &vaux1 {
> > 	/* Needed for ads7846 */
> > 	regulator-name = "vcc";
> > };
> > 
> > &vpll2 {
> > 	/* Needed for DSS */
> > 	regulator-name = "vdds_dsi";
> > };

In the long we'll use regulator phandles anyways in the DSS related
nodes, so from that point of view fixing dpi.c makes sense.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 11/11] OMAPDSS: DPI: use VPLL2 regulator if VDDS_DSI is not found
Date: Sat, 16 Nov 2013 07:45:07 -0800	[thread overview]
Message-ID: <20131116154507.GL10317@atomide.com> (raw)
In-Reply-To: <5287908C.3040602@collabora.co.uk>

* Javier Martinez Canillas <javier.martinez@collabora.co.uk> [131116 07:36]:
> Hi Tony,
> 
> On 11/16/2013 03:18 PM, Tony Lindgren wrote:
> > * Javier Martinez Canillas <javier.martinez@collabora.co.uk> [131116 05:25]:
> >> On Device Tree boot the VDDS_DSI regulator is not linked to
> >> the DPI device so omapfb driver probing fails with:
> >> 
> >> [    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
> >> 
> >> As a workaround try to use the VPLL2 regulator from twl4030 in
> >> dpi_init_regulator() if getting the VDDS_DSI regulator fails.
> > 
> > Probably makes sens to fix this in the dpi.c, but this can also be set
> > in the .dts file. I just set up the following in the omap3-ldp.dts file:
> > 
> 
> Sorry is not clear to me if you agree that makes sense to do this fix on dpi.c
> or if you think this is a bad idea and prefer to do it in the DTS instead?
> 
> I'm asking to know if I have to send a follow up patch or not :)

Well let's see what Tomi prefers.

> > &vaux1 {
> > 	/* Needed for ads7846 */
> > 	regulator-name = "vcc";
> > };
> > 
> > &vpll2 {
> > 	/* Needed for DSS */
> > 	regulator-name = "vdds_dsi";
> > };

In the long we'll use regulator phandles anyways in the DSS related
nodes, so from that point of view fixing dpi.c makes sense.

Regards,

Tony

  reply	other threads:[~2013-11-16 15:45 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-16 13:23 [PATCH 00/11]: add remaining support for IGEP boards Javier Martinez Canillas
2013-11-16 13:23 ` Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 01/11] ARM: dts: omap3-igep: Fix bus-width for mmc1 Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 02/11] ARM: dts: omap3-igep: Add support for LBEE1USJYC WiFi connected to SDIO Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 03/11] ARM: dts: omap3-igep: Update to use the TI AM/DM37x processor Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 14:44   ` Tony Lindgren
2013-11-16 14:44     ` Tony Lindgren
2013-11-16 15:19     ` Javier Martinez Canillas
2013-11-16 15:19       ` Javier Martinez Canillas
2013-11-16 15:22       ` Tony Lindgren
2013-11-16 15:22         ` Tony Lindgren
2013-11-16 13:23 ` [PATCH 04/11] ARM: dts: omap3-igep0020: Add pinmux setup for i2c devices Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 05/11] ARM: dts: omap3-igep0020: Add pinmuxing for DVI output Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 06/11] ARM: dts: AM33XX BASE0033: add pinmux and hdmi node to enable display Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 07/11] ARM: dts: AM33XX BASE0033: add pinmux and user led support Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 08/11] ARM: dts: AM33XX BASE0033: add 32KBit EEPROM support Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 09/11] ARM: dts: AM33XX IGEP0033: add USB support Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 10/11] ARM: OMAP: dss-common: change IGEP's DVI DDC i2c bus Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 13:23 ` [PATCH 11/11] OMAPDSS: DPI: use VPLL2 regulator if VDDS_DSI is not found Javier Martinez Canillas
2013-11-16 13:23   ` Javier Martinez Canillas
2013-11-16 14:18   ` Tony Lindgren
2013-11-16 14:18     ` Tony Lindgren
2013-11-16 15:34     ` Javier Martinez Canillas
2013-11-16 15:34       ` Javier Martinez Canillas
2013-11-16 15:45       ` Tony Lindgren [this message]
2013-11-16 15:45         ` Tony Lindgren
2013-11-16 16:02         ` Sebastian Reichel
2013-11-16 16:02           ` Sebastian Reichel
2013-11-16 17:28           ` Javier Martinez Canillas
2013-11-16 17:28             ` Javier Martinez Canillas
2013-11-17  0:26             ` Sebastian Reichel
2013-11-17  0:26               ` Sebastian Reichel
2013-11-17  1:06               ` Javier Martinez Canillas
2013-11-17  1:06                 ` Javier Martinez Canillas
2013-11-16 14:16 ` [PATCH 00/11]: add remaining support for IGEP boards Tony Lindgren
2013-11-16 14:16   ` Tony Lindgren
2013-11-16 14:41   ` Javier Martinez Canillas
2013-11-16 14:41     ` Javier Martinez Canillas

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=20131116154507.GL10317@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=eballetbo@gmail.com \
    --cc=javier.martinez@collabora.co.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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: link
Be 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.