From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
Thierry Reding <thierry.reding@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] drm: Use new DRM_BUS_FLAG_*_(DRIVE|SAMPLE)_(POS|NEG)EDGE flags
Date: Mon, 10 Dec 2018 01:51:53 +0200 [thread overview]
Message-ID: <1639330.R4tVfZHe6a@avalon> (raw)
In-Reply-To: <9b0969b8-f0ad-1c95-7eb0-f36044466ada@ti.com>
Hi Tomi,
On Wednesday, 5 December 2018 12:42:12 EET Tomi Valkeinen wrote:
> On 05/12/18 10:49, Laurent Pinchart wrote:
> > From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> >
> > The DRM_BUS_FLAG_PIXDATA_(POS|NEG)EDGE and
> > DRM_BUS_FLAG_SYNC_(POS|NEG)EDGE flags are deprecated in favour of the
> > new DRM_BUS_FLAG_PIXDATA_(DRIVE|SAMPLE)_(POS|NEG)EDGE and
> > new DRM_BUS_FLAG_SYNC_(DRIVE|SAMPLE)_(POS|NEG)EDGE flags. Replace them
> > through the code.
> >
> > This effectively changes the value of the .sampling_edge bridge timings
> > field in the dumb-vga-dac driver. This is safe to do as no driver
> > consumes these values yet.
>
> When to use which?
The idea is to use the flags that correspond to the side corresponding to the
code. A bridge driver, in its input_bus_flags, would use the sample flags. A
display controller driver would likely use the drive flags. If we later extend
drm_bridge to handle polarities on the source side of the bridge, the drive
flags should be used there.
It also makes sense to follow the perspective described in datasheets and
hardware registers. If an internal encoder is documented using the driving
perspective for its input signals, usage of the drive flags is likely best.
In a nutshell, use the flags that result in the simplest possible code.
> Looking at the omap drivers, you use the DRIVE variant. But if the
> encoder/panel is describing what it wants as input, shouldn't it use the
> SAMPLE variant?
I have to confess I haven't paid much attention to the omapdrm/displays/
drivers as we're in the process of removing them, but I think you're right
there. For the SDI encoder, the datasheet documents polarities from a drive
perspective, so I've kept that. For the DSI encoder there's no documented
polarities, so I used the drive perspective there as well to remain
consistent.
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-12-09 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 8:49 [PATCH v2 0/2] Clarify display info PIXDATA bus flags Laurent Pinchart
2018-12-05 8:49 ` [PATCH v2 1/2] drm: Clarify definition of the DRM_BUS_FLAG_(PIXDATA|SYNC)_* macros Laurent Pinchart
2018-12-05 8:49 ` [PATCH v2 2/2] drm: Use new DRM_BUS_FLAG_*_(DRIVE|SAMPLE)_(POS|NEG)EDGE flags Laurent Pinchart
2018-12-05 10:42 ` Tomi Valkeinen
2018-12-05 12:21 ` Stefan Agner
2018-12-09 23:52 ` Laurent Pinchart
2018-12-09 23:51 ` Laurent Pinchart [this message]
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=1639330.R4tVfZHe6a@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=thierry.reding@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.