LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Kevin Quigley <kevin@kquigley.co.uk>,
	Andrzej Hajda <a.hajda@samsung.com>,
	"dri-devel\@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	James Hughes <james.hughes@raspberrypi.org>,
	Archit Taneja <architt@codeaurora.org>
Subject: RE: [PATCH] drm/vc4: Enable the DSI module and link before other enables.
Date: Thu, 21 Jun 2018 16:19:24 -0700	[thread overview]
Message-ID: <87a7rnenib.fsf@anholt.net> (raw)
In-Reply-To: <C15157EF5067BD40AA5332C0BEB5F4D3079020E596F6@quiclu02.quigley.local>

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

Kevin Quigley <kevin@kquigley.co.uk> writes:

> Hi,
>
> When we talk about control bus enable and video transfer enable for
> DSI, there is a mode in which control commands can be sent,
> interleaved with the video.  This is often done at the end-of-frame
> and/or end of line.  I've seen this handled in some other DSI device
> drivers.  In these cases, the driver has to look at the frame timing
> in the video and carefully select the number of control bytes which
> can be sent during the blanking periods.  The number of bytes which
> can be sent, is very much dependant on the panel-size and clock
> frequencies... (which determines the blanking time).  I'm not sure how
> widely this is a feature in the DSI encoder HW, and/or implemented
> purely in the drivers.

That scheduling is done by the VC4 DSI encoder.

> To conclude: I think that DSI encoder devices need to be able to
> support sending control data (LPDA) - concurrently with video frames.

I believe that should work already.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2018-06-21 23:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180604194448epcas1p29627759e2d8c0b1388c6700a7da77a45@epcas1p2.samsung.com>
2018-06-04 19:44 ` Eric Anholt
2018-06-05  8:25   ` Andrzej Hajda
2018-06-05 18:49     ` Eric Anholt
2018-06-06  8:28       ` Andrzej Hajda
2018-06-07 17:22     ` Kevin Quigley
2018-06-21 23:19       ` Eric Anholt [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=87a7rnenib.fsf@anholt.net \
    --to=eric@anholt.net \
    --cc=a.hajda@samsung.com \
    --cc=architt@codeaurora.org \
    --cc=boris.brezillon@bootlin.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=james.hughes@raspberrypi.org \
    --cc=kevin@kquigley.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --subject='RE: [PATCH] drm/vc4: Enable the DSI module and link before other enables.' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).