From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Vikas Patil <vikasmpatil@gmail.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [ADV7393] DRM Encoder Slave or DRM Bridge
Date: Mon, 26 Sep 2016 15:30:04 +0300 [thread overview]
Message-ID: <db77d593-41ce-7617-56fd-684a0b5fd28d@ti.com> (raw)
In-Reply-To: <CA+kt3u1Oa7ThN5gu5yxk=0xwUmZhLp+TL+=sX4zBvaj41FY2Uw@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2556 bytes --]
On 26/09/16 15:25, Vikas Patil wrote:
> On Fri, Sep 23, 2016 at 4:30 PM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
>> On 22/09/16 16:22, Vikas Patil wrote:
>>
>>> Could you help me to understand if I could use “interlace=false”?
>>> ADV7393 seems to be supporting non-interlaced mode. From datasheet:
>>> “The ADV7390/ADV7391/ADV7392/ADV7393 support an SD noninterlaced mode.
>>> Using this mode, progressive inputs at twice the frame rate of NTSC
>>> and PAL (240p/59.94 Hz and 288p/50 Hz, respectively) can be input into
>>> the ADV7390/ ADV7391/ADV7392/ADV7393. The SD noninterlaced mode can be
>>> enabled using Subaddress 0x88, Bit 1.”
>>
>> Difficult to say... So OMAP4+ DSS hardware does support interlace output
>> for DPI. The driver has never supported it, nor do I have any hardware
>> to test it. It might be quite easy to add, though.
>>
> If it is easy and doable then could you describe what I need to do to
> support it?
I think there are a few problems there, as the analog connector wasn't
designed to support detection. But you can check the detect callback
from the encoder/connector drivers.
The problem is, it returns a bool, whereas we need a tristate return
value here to represent connected, not connected, unknown.
>> If I read the above snippet right, to use progressive input, the DISPC
>> needs to output at double refresh rate. So probably what you would have
>> to do is in ADV driver, you have your set_timings function, where you
>> should double the pix clock before you pass the timings forward to the
>> DISPC's DPI driver.
>>
>
> I have configured ADV7393 chip in following mode with the timing below
> in connector-analog.tv.c. With this I am seeing continuous flicker
> with nothing on display (black screen) and sometime could see the
> kmscube but it seems it renders in four quadrant(i.e. once in each
> quadrant). I have also tried doubling the pixel clock from 27MHz to
> 54MHz in timing for non-interlaced mode of ADV7393 but with it also
> nothing on display and continuous flicker.
>
> Do you know what might be going wrong? What should I look for to fix this?
>
> ** ADV config:
> - 16-bit SD RGB input
> - NTSC mode
> - YPrPb component output (CVBS)
> - non-interlaced mode
>
> ** Timing configured in in connector-analog.tv.c
>
> static const struct omap_video_timings harman_ntsc_timings = {
> .x_res = 720,
> .y_res = 480,
> .pixelclock = 270000000,
That's 270MHz.
Tomi
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-26 12:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 12:29 [ADV7393] DRM Encoder Slave or DRM Bridge Vikas Patil
2016-09-13 8:47 ` Vikas Patil
2016-09-13 8:57 ` Tomi Valkeinen
2016-09-13 13:13 ` Vikas Patil
2016-09-14 9:34 ` Tomi Valkeinen
2016-09-15 9:44 ` Vikas Patil
2016-09-15 9:53 ` Tomi Valkeinen
2016-09-21 10:59 ` Vikas Patil
2016-09-22 13:22 ` Vikas Patil
2016-09-23 10:08 ` Vikas Patil
2016-09-23 11:02 ` Tomi Valkeinen
2016-09-26 6:57 ` Vikas Patil
2016-09-26 11:55 ` Tomi Valkeinen
2016-09-23 11:00 ` Tomi Valkeinen
2016-09-26 12:25 ` Vikas Patil
2016-09-26 12:30 ` Tomi Valkeinen [this message]
2016-09-26 12:34 ` Vikas Patil
2016-09-26 12:41 ` Tomi Valkeinen
2016-09-26 12:46 ` Vikas Patil
2016-09-18 10:15 ` Laurent Pinchart
2019-05-27 11:21 ` Nasser
-- strict thread matches above, loose matches on Subject: below --
2019-05-27 1:07 nasser afshin
2019-05-27 6:19 ` Daniel Vetter
2019-05-27 7:19 ` Vikas Patil
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=db77d593-41ce-7617-56fd-684a0b5fd28d@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=vikasmpatil@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox