From: Daniel Drake <dsd@laptop.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 2/2] viafb: Add OLPC XO-1.5 port configs
Date: Sun, 26 Sep 2010 14:57:23 +0000	[thread overview]
Message-ID: <AANLkTim-cmTwc_pJ0AwB15hEBS2kXfOMTyku9CWhwBka@mail.gmail.com> (raw)
In-Reply-To: <20100921153726.21D609D401B@zog.reactivated.net>
On 21 September 2010 18:54, Florian Tobias Schandinat
<FlorianSchandinat@gmx.de> wrote:
> *after a deeper look at the patch*
> Hm, one of my patches enables 0x26 also as I2C. So the only difference
> between the current config and your config is whether 0x2c is GPIO or I2C
> where your version make a lot more sense.
> Jon, do you agree that this should become the default config?
> Handling a GPIO device as such and not as an I2C device sounds right to me,
> although we have to take care about the old code which is doing so.
Jon, ping :)
Something possibly of relevance:
In addition to enabling the camera and DCON, changing the port config
of 0x2c from VIA_MODE_I2C to VIA_MODE_GPIO makes a fairly substantial
difference in the viafb init paths for XO-1.5.
On linus master, before making the change in my patch, viafb init
takes a long time, maybe 10 seconds. With linux-next 20100924, it
takes 2.5 seconds. After the patch, it takes 0.07 seconds.
Timings from linux-next:
[    1.021495] VIA Graphics Intergration Chipset framebuffer 2.4 initializing
[    1.029309] viafb 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    2.970023] viafb_init_dvi_size: DVI panel size undetected!
[    3.475728] Console: switching to colour frame buffer device 100x40
And from the same kernel with the port config adjusted:
[    1.025436] VIA Graphics Intergration Chipset framebuffer 2.4 initializing
[    1.033234] viafb 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.057799] viafb_init_dvi_size: DVI panel size undetected!
[    1.090548] Console: switching to colour frame buffer device 100x40
So, changing this value makes a pretty significant difference. If you
changed it globally I'm wondering if you'd be breaking current non-XO
systems, for example you'd be presumably affecting the behaviour of
viafb_lvds_trasmitter_identify()
At the same time, I don't fully understand what these port configs
actually are, so I might be far off point.
Daniel
next prev parent reply	other threads:[~2010-09-26 14:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 15:37 [PATCH 2/2] viafb: Add OLPC XO-1.5 port configs Daniel Drake
2010-09-21 17:15 ` Florian Tobias Schandinat
2010-09-21 17:15 ` Daniel Drake
2010-09-21 17:54 ` Florian Tobias Schandinat
2010-09-26 14:57 ` Daniel Drake [this message]
2010-09-26 15:50 ` Florian Tobias Schandinat
2010-09-26 15:57 ` Daniel Drake
2010-09-26 21:52 ` Jonathan Corbet
2010-09-27  4:55 ` Florian Tobias Schandinat
2010-10-06 21:15 ` Jonathan Corbet
2010-10-27 15:08 ` Daniel Drake
2010-10-28 18:51 ` Jonathan Corbet
2010-10-28 21:54 ` Daniel Drake
2010-10-28 22:04 ` Jonathan Corbet
2010-10-29 14:03 ` Daniel Drake
2010-11-11 14:59 ` Daniel Drake
2010-11-11 16:01 ` Florian Tobias Schandinat
2010-11-11 17:07 ` Daniel Drake
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=AANLkTim-cmTwc_pJ0AwB15hEBS2kXfOMTyku9CWhwBka@mail.gmail.com \
    --to=dsd@laptop.org \
    --cc=linux-fbdev@vger.kernel.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).