linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Miao <eric.y.miao@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 7/8] pxa: add frame buffer on pxa168 aspenite platform
Date: Fri, 20 Nov 2009 04:56:45 +0000	[thread overview]
Message-ID: <f17812d70911192056m64b31c62hd050c0567e098cb@mail.gmail.com> (raw)
In-Reply-To: <7c34ac520911191838k45fa4708vd8b606e9ad6a8d7@mail.gmail.com>

On Thu, Nov 19, 2009 at 8:38 PM, Jun Nie <niej0001@gmail.com> wrote:
> 2009/11/20 Eric Miao <eric.y.miao@gmail.com>:
>>> +       int err = 0;
>>> +       if (on) {
>>> +               if (spi_gpio_reset != -1) {
>>> +                       err = gpio_request(spi_gpio_reset, "TPO_LCD_SPI_RESET");
>>> +                       if (err) {
>>> +                               printk(KERN_ERR "failed to request GPIO for TPO LCD RESET\n");
>>> +                               return err;
>>> +                       }
>>> +                       gpio_direction_output(spi_gpio_reset, 0);
>>> +                       msleep(100);
>>
>> This is really a loooong delay, there any specific reason for such a long
>> delay, I'm seeing this to slow down the boot up significantly?
>>
>> Otherwise looks OK to me, and I prefer the defconfig file change to
>> be a separate patch please.
>>
>
> Actually, This is just an example for other real products. There is no
> such spi_reset pin on Aspenite , so machine info set it spi_gpio_reset
> = -1. Or do you think we should delete these lines?
>

I see no reason for it to stay there then, please remove.

  reply	other threads:[~2009-11-20  4:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10  8:12 [PATCH 7/8] pxa: add frame buffer on pxa168 aspenite platform Jun Nie
2009-11-12  2:19 ` Jun Nie
2009-11-16  9:34 ` Jun Nie
2009-11-17  6:29   ` Eric Miao
2009-11-19  9:03     ` Jun Nie
2009-11-19 16:29       ` Eric Miao
2009-11-20  2:38         ` Jun Nie
2009-11-20  4:56           ` Eric Miao [this message]
2009-11-23  5:52             ` Jun Nie

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=f17812d70911192056m64b31c62hd050c0567e098cb@mail.gmail.com \
    --to=eric.y.miao@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).