From: Jyri Sarha <jsarha@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>, dri-devel@lists.freedesktop.org
Cc: peter.ujfalusi@ti.com, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH v2 2/3] drm/omapdrm: Work-a-round for errata i734 (LCD1 Gamma) in DSS dispc
Date: Tue, 24 May 2016 00:02:23 +0300 [thread overview]
Message-ID: <57436FDF.8000406@ti.com> (raw)
In-Reply-To: <57431C69.60709@ti.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1443 bytes --]
On 05/23/16 18:06, Tomi Valkeinen wrote:
>> For gamma tables to work on LCD1 the GFX plane has to be used at least
>> > once after DSS HW has come out of reset. The work-a-round sets up a
>> > minimal LCD setup with GFX plane and waits for one vertical sync irq
>> > before disabling the setup and continuing with the context
>> > restore. The physical outputs are gated during the operation. This
>> > work-a-round requires that gamma table's LOADMODE is set to 0x2 in
>> > DISPC_CONTROL1 register.
> This LOADMODE comment is a bit odd. You should say why, and how it's
> handled, and what's "0x2". But then, I'm not sure if the whole comment
> is needed at all. The driver is made to work only with LOADMODE=2.
>
It is there also in the comment and my point is to notify that if the
gamma support is ever changed to use some other mode, the workaround
needs to change too.
It is pretty hard to draw the line to how deep in details one should go
in comments or commit descriptions. I added the register name so that
someone is interested he can find the full description of the LOADMODE
from TRM using that as a key word.
I think I wont mention the LOADMODE in the description but leave it on
the code comments.
> Maybe the real point here is that the WA needs to happen after the
> initial DSS register config.
>
I think that detail should be in the code comments, if it is needed at all.
BR,
Jyri
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 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-05-23 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 14:41 [PATCH v2 0/3] drm/omapdrm: gamma table support Jyri Sarha
2016-05-23 14:41 ` [PATCH v2 1/3] drm/omapdrm: Add gamma table support to DSS dispc Jyri Sarha
2016-05-23 14:41 ` [PATCH v2 2/3] drm/omapdrm: Work-a-round for errata i734 (LCD1 Gamma) in " Jyri Sarha
2016-05-23 15:00 ` Jyri Sarha
2016-05-23 15:06 ` Tomi Valkeinen
2016-05-23 21:02 ` Jyri Sarha [this message]
2016-05-23 14:41 ` [PATCH v2 3/3] drm/omapdrm: Implement gamma_lut atomic crtc property Jyri Sarha
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=57436FDF.8000406@ti.com \
--to=jsarha@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=peter.ujfalusi@ti.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.