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 14:55:45 +0300 [thread overview]
Message-ID: <4d4e32bb-d2be-aef7-236c-d25dbd00360e@ti.com> (raw)
In-Reply-To: <CA+kt3u18taFLfvnJN43zvYKNT9Nydc8ze4z4iwH7N3tBGWWREg@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1020 bytes --]
On 26/09/16 09:57, Vikas Patil wrote:
> On Fri, Sep 23, 2016 at 4:32 PM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
>> On 23/09/16 13:08, Vikas Patil wrote:
>>> Hi Tomi,
>>>
>>> I added the missing check for "OMAP_DISPLAY_TYPE_VENC" in function
>>> omap_connector_detect @ gpu/drm/omapdrm/omap_connector.c and now
>>> modetest seems to be showing correct status and connections.
>>
>> Is there a cable detection support in the ADV hardware & driver? If not,
>> then the cable connection status is "unknown". It should still work if
>> the output is enabled manually. I think. I don't have any boards with
>> analog tv out..
>>
>
> It seems adv7393 has the support for "cable detection" but I am not
> sure How to utilize it in driver? Also what ddi you mean by " It
You can see hdmi for examples. But it should work fine without the
detection.
> should still work if
> the output is enabled manually."?
The userspace should be able to enable a connector with unknown status.
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 11:55 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 [this message]
2016-09-23 11:00 ` Tomi Valkeinen
2016-09-26 12:25 ` Vikas Patil
2016-09-26 12:30 ` Tomi Valkeinen
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=4d4e32bb-d2be-aef7-236c-d25dbd00360e@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