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: Wed, 14 Sep 2016 12:34:16 +0300 [thread overview]
Message-ID: <3958e459-2127-4450-9749-913365949996@ti.com> (raw)
In-Reply-To: <CA+kt3u2SNx1L-3T6gEHaD5ijkNEwDiTSqavsHDmh6yQqH_V3yQ@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1054 bytes --]
On 13/09/16 16:13, Vikas Patil wrote:
> Thanks Tomi for quick comment.
>
> I am thinking to base adv7393 driver on
> "drivers\gpu\drm\omapdrm\displays\encoder-tc358768.c" as I don't think
> any similar to adv7393 chip driver available. Could you please comment
> if this will help to get adv chip running?
I presume you're not using mainline kernel, as that driver is not there.
I'm not familiar with adv7393, but yes, I think you can use that as an
example.
> I tried to add the device tree config but after adding device
> configuration related to adv7393, my first display stopped working and
> whenever I run kmscube or modetest it fails.
If you don't have all the display pipelines working (i.e. the drivers
present and working), none of the displays will work.
> I have following configuration related to displays. Could anyone tell
> me if I am doing anything wrong in DTS configuration? What could be
> going wrong when I enable adv7393 related config so display 1 stops
> working?
The dts looks ok.
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-14 9:34 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 [this message]
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
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
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=3958e459-2127-4450-9749-913365949996@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.