All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikas Patil <vikasmpatil@gmail.com>
To: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Valkeinen, Tomi" <tomi.valkeinen@ti.com>,
	Rob Clark <robdclark@gmail.com>,
	architt@codeaurora.org
Subject: Re: [ADV7393] DRM Encoder Slave or DRM Bridge
Date: Tue, 13 Sep 2016 14:17:25 +0530	[thread overview]
Message-ID: <CA+kt3u0SxoK6zwsuSkBggQZXrryzzeY5hzwdv_jvZrnWv_RT9Q@mail.gmail.com> (raw)
In-Reply-To: <CA+kt3u11xsbjhZ2mNRfJUBbqtrPaUJHsEMk9CfzLdEED=xBXSw@mail.gmail.com>

Dear All,

I also see some of the encoder driver are at
"drivers/gpu/drm/omapdrm/displays/". I am confused about which driver
I should consider for reference for adv7393 driver development.

Do I need to use
"drivers/gpu/drm/omapdrm/displays/connector-analog-tv.c" too along
with adv7393 driver?

Thanks & Regards,
Vikash

On Mon, Sep 12, 2016 at 5:59 PM, Vikas Patil <vikasmpatil@gmail.com> wrote:
> Dear All,
>
> I am trying to understand difference between "DRM Encoder slave
> driver" and "DRM bridge driver" as I need to write one for ADV7393
> Video Encoder Chip for the custom target
> based on DRA74x having following display connection.
>
> VOUT1 --> ADV7393 --> CVBS Out    (ADV7393 is on I2C)
>
> Could anyone here explain what is the difference between two and which
> I need to implement for ADV7393 and why?
>
> I could see adv7393 driver available at "drivers/media/i2c/adv7393.c"
> in linux 4.4.14. Can I use this driver? My feeling is I can not use
> but why could not much understand.
> or Do I need to base my driver something like
> "drivers/gpu/drm/i2c/adv7511.c", however I also see it is converted to
> bridge driver and moved to  "drivers/gpu/drm/bridge/adv7511.c" [1]
>
> [1] http://www.spinics.net/lists/dri-devel/msg113244.html
>
> Thanking you all in advance.
>
> Thanks & Regards,
> Vikash
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-09-13  8:47 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 [this message]
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
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=CA+kt3u0SxoK6zwsuSkBggQZXrryzzeY5hzwdv_jvZrnWv_RT9Q@mail.gmail.com \
    --to=vikasmpatil@gmail.com \
    --cc=architt@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robdclark@gmail.com \
    --cc=tomi.valkeinen@ti.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.