All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Salveti de Araujo <ricardo.salveti@canonical.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: linux-omap@vger.kernel.org, charu@ti.com
Subject: Re: [PATCH v2 2/2] omap3: beaglexm: fix DVI initialization
Date: Wed, 09 Feb 2011 09:47:09 -0200	[thread overview]
Message-ID: <1297252029.15396.4.camel@evatp> (raw)
In-Reply-To: <AANLkTin9VRwgMyw9LUr691n++QByq14JGdARwN3ZVqW0@mail.gmail.com>

On Wed, 2011-02-09 at 12:23 +0530, G, Manjunath Kondaiah wrote:
> On Wed, Feb 9, 2011 at 1:13 AM, Ricardo Salveti de Araujo
> <ricardo.salveti@canonical.com> wrote:
> > Function beagle_twl_gpio_setup is called after beagle_display_init, what
> > lets reset_gpio with an invalid value at the time it request the gpio.
> > As a side effect the DVI reset GPIO is not properly set.
> >
> > Also removing old code that powers down DVI in a hardcoded way, as it's
> > not necessary anymore.
> >
> > Tested with Beagle-xM and C4.
> 
> Surprised to see if this code works on C4 since there is gpio_request
> for gpio_170 in the beagle init code
> (linux omap master branch) which is before beagle_display_init()
> 
>         omap_mux_init_gpio(170, OMAP_PIN_INPUT);
>         gpio_request(170, "DVI_nPD");
>         /* REVISIT leave DVI powered down until it's needed ... */
>         gpio_direction_output(170, true);
> 
> The second gpio_request(for 170) should fail in beagle_display_init.
> Pls check and confirm.

That's why this part is also removed at my patch.

Cheers,
--
Ricardo Salveti de Araujo


  reply	other threads:[~2011-02-09 11:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 19:43 [PATCH v2 0/2] beagle: making DVI output work again Ricardo Salveti de Araujo
2011-02-08 19:43 ` [PATCH v2 1/2] omap3: beagle: adding regulator supply for vdds_sdi Ricardo Salveti de Araujo
2011-02-08 19:43 ` [PATCH v2 2/2] omap3: beaglexm: fix DVI initialization Ricardo Salveti de Araujo
2011-02-09  0:07   ` Varadarajan, Charulatha
2011-02-09  6:53   ` G, Manjunath Kondaiah
2011-02-09 11:47     ` Ricardo Salveti de Araujo [this message]
2011-02-09 11:53       ` G, Manjunath Kondaiah

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=1297252029.15396.4.camel@evatp \
    --to=ricardo.salveti@canonical.com \
    --cc=charu@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=manjugk@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.