From: Magnus Damm <magnus.damm@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 00/02] sh: Panning fixes
Date: Mon, 15 Feb 2010 10:33:22 +0000 [thread overview]
Message-ID: <aec7e5c31002150233r3fd5c8fcma94842699bb0073d@mail.gmail.com> (raw)
In-Reply-To: <AB12B32E73474741A2C5361C433A44DE0178367D@rte-ben-exch.RTE.ADWIN.RENESAS.COM>
Hi Phil,
On Mon, Feb 15, 2010 at 5:41 PM, Phil Edworthy
<Phil.Edworthy@renesas.com> wrote:
>> >> Thanks for your patches. Please make sure that the SYS panel case with
>> >> deferred io is working. Migo-R is a good board to test this on.
>> >
>> > I thought the Migo-R doesn't have vsync connected to the SH, so maybe
>> this
>> > patch won't show any difference. Is that your understanding?
>>
>> Something like that, I think the QVGA LCD panel on Migo-R does not
>> expose the VSYNC pin of the on-panel LCD controller so there is
>> nothing to connect to the sh7722.
> That's what I thought.
So there will be tearing on Migo-R regardless how smart our software is...
>> It may be difficult to test your patch because of this, I'm not sure.
>> My main concern was just to double check that you've thought about
>> dealing with both the deferred io case and the "regular" non-deferred
>> io case. The sh7724 KFR2R09 board is using deferred io and I think
>> some upcoming boards may make use of that as well, so I'd prefer to
>> keep that case working. =)
>
> How do you want to proceed then? I can't say that I am familiar with
> deferred io and I don't have a board I can test it on... Is there anyone you
> know who can try this?
... but it should be possible to test on Migo-R even though the vsync
pin is missing.
Usually people who submit patches do the testing to make sure other
platforms won't break. I realize that it may be difficult for you if
you don't have any platform to test on.
I may be able to find a Migo-R board somewhere, and I'd be happy to
add this to my TODO list. Beware that my list is pretty long, so if
you're in a rush then I suggest you to test yourself or find someone
else to do it for you.
Cheers,
/ magnus
next prev parent reply other threads:[~2010-02-15 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 10:23 [PATCH 00/02] sh: Panning fixes Phil Edworthy
2010-02-12 2:51 ` Magnus Damm
2010-02-12 10:45 ` Phil Edworthy
2010-02-13 14:35 ` Magnus Damm
2010-02-15 8:41 ` Phil Edworthy
2010-02-15 10:33 ` Magnus Damm [this message]
2010-02-15 10:40 ` Phil Edworthy
2010-02-15 10:55 ` Magnus Damm
2010-02-15 11:58 ` Phil Edworthy
2010-02-15 12:05 ` Guennadi Liakhovetski
2010-02-15 12:08 ` Phil Edworthy
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=aec7e5c31002150233r3fd5c8fcma94842699bb0073d@mail.gmail.com \
--to=magnus.damm@gmail.com \
--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).