linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: rcar-h2 du issue between du0 and du2
Date: Wed, 13 Nov 2013 10:24:51 +0000	[thread overview]
Message-ID: <52835373.8000907@codethink.co.uk> (raw)
In-Reply-To: <52825196.1090102@codethink.co.uk>

On 13/11/13 02:44, Laurent Pinchart wrote:
> Hi Ben,
>
> On Tuesday 12 November 2013 16:04:38 Ben Dooks wrote:
>> I am using the 3.4 renesas backport (0.5.1) and having issue with the
>> rcar_du driver with any du0 and du2 having seperate operating modes.
>>
>> du2 seems to be picking up the data width of du0, so if du0 is at
>> 1920x1080 and du2 at 800x600, du2 will show a display as if du2 data
>> was at a 1920 stride.
>>
>> If both du0 and du2 are at 800x600 then both show the right display
>> data,
>
> Ouch. Thank you for the report. I'll test and debug that. What's the urgency
> level ?

Medium, there's other stuff that I can be getting on with.

I've been looking through the H2 manual but there's nothing specifically
saying the DU0 and DU2 planes should be linked. I know DU0_0 and DU0_1
are basically linked.

We are using the Lager board as following:

We have DU0 outputting LVDS to the ADV7511 to provide DVI
DU2 is connected to the DPAD0 to the VGA

DU0 is configured for 1920x1080-60, 32bpp
DU2 is configured for 800x600-60, 32bpp

DU2 has been verified as outputting 800x600-60 display timings.


-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

  parent reply	other threads:[~2013-11-13 10:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 16:04 rcar-h2 du issue between du0 and du2 Ben Dooks
2013-11-13  2:44 ` Laurent Pinchart
2013-11-13 10:24 ` Ben Dooks [this message]
2013-11-14 12:52 ` Ben Dooks
2013-11-14 13:24 ` Laurent Pinchart

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=52835373.8000907@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --cc=linux-sh@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).