public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: archit taneja <archit@ti.com>
To: Bryan Wu <bryan.wu@canonical.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"tony@atomide.com" <tony@atomide.com>,
	"kernel-team@lists.ubuntu.com" <kernel-team@lists.ubuntu.com>
Subject: Re: [PATCH] omap3: Adding vdd_sdi regulator supply to OMAP3EVM
Date: Mon, 21 Feb 2011 13:54:00 +0530	[thread overview]
Message-ID: <4D622120.20209@ti.com> (raw)
In-Reply-To: <AANLkTim7Ks2n0CymKWSjpd2ND7ee1H_wKZDANBym7dnZ@mail.gmail.com>

Hi,

On Monday 21 February 2011 12:32 PM, Bryan Wu wrote:
> Hi, would you guys take a look at this?
>
> Thanks,
> -Bryan
>
> On Thu, Feb 17, 2011 at 4:11 PM, Bryan Wu<bryan.wu@canonical.com>  wrote:
>> From: Mathieu J. Poirier<mathieu.poirier@canonical.com>
>>
>> https://bugs.launchpad.net/bugs/630885
>>
>> When booting, the omapdss subsystem is looking for a regulator named
>> "vdds_sdi". When the regulator is not found the initialisation sequence
>> is aborted resulting in omapfb not finding a display to work with.  This
>> patch allows the omapfb sub system to complete its initialisation
>> properly and enable LCD display. The problem was fixed by lumping a
>> "vdds_sdi" with the already existing "vdds_dsi" regulator. This fix
>> takes its root from work done on the Beagle board and the Pandora board.
>>
>> Signed-off-by: Mathieu Poirier<mathieu.poirier@canonical.com>
>> Signed-off-by: Andy Whitcroft<apw@canonical.com>
>> Signed-off-by: Bryan Wu<bryan.wu@canonical.com>
>> ---
>>   arch/arm/mach-omap2/board-omap3evm.c |   10 ++++++----
>>   1 files changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/board-omap3evm.c b/arch/arm/mach-omap2/board-omap3evm.c
>> index c2a0fca..8b8eb36 100644
>> --- a/arch/arm/mach-omap2/board-omap3evm.c
>> +++ b/arch/arm/mach-omap2/board-omap3evm.c
>> @@ -521,8 +521,10 @@ static struct regulator_init_data omap3_evm_vdac = {
>>   };
>>
>>   /* VPLL2 for digital video outputs */
>> -static struct regulator_consumer_supply omap3_evm_vpll2_supply =
>> -       REGULATOR_SUPPLY("vdds_dsi", "omapdss");
>> +static struct regulator_consumer_supply omap3_evm_vdds_supplies[] = {
>> +       REGULATOR_SUPPLY("vdds_sdi", "omapdss"),
>> +       REGULATOR_SUPPLY("vdds_dsi", "omapdss"),
>> +};

I agree that this is needed. Currently, in omap_dss_probe() in core.c we 
call sdi_init even if its not selected in menuconfig. The same goes for 
other modules.

There is no harm adding this as. But we will probably need a cleaner way 
to handle initialization of the DSS interface modules in the DSS2 code.

Regards,
Archit

  reply	other threads:[~2011-02-21  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17  8:11 [PATCH] omap3: Adding vdd_sdi regulator supply to OMAP3EVM Bryan Wu
2011-02-21  7:02 ` Bryan Wu
2011-02-21  8:24   ` archit taneja [this message]
2011-02-21  9:08 ` 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=4D622120.20209@ti.com \
    --to=archit@ti.com \
    --cc=bryan.wu@canonical.com \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-omap@vger.kernel.org \
    --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: link
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