From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Ricardo Neri <ricardo.neri@ti.com>
Cc: archit@ti.com, s-guiriec@ti.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH v3 RESEND] OMAPDSS: DISPC: Improvements to DIGIT sync signal selection
Date: Wed, 01 Aug 2012 09:28:41 +0300 [thread overview]
Message-ID: <1343802521.2645.6.camel@deskari> (raw)
In-Reply-To: <1343779019-10611-1-git-send-email-ricardo.neri@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
On Tue, 2012-07-31 at 18:56 -0500, Ricardo Neri wrote:
> DSS code wrongly assumes that VENC is always available as source for the external
> sync signal for the display controller DIGIT channel. One cannot blindly write/read
> the value of DSS_CONTROL[15] as in certain processors (e.g., OMAP5) this operation
> may not be valid. If the the sync source is not read correctly, the callers of
> dss_get_hdmi_venc_clk_source might make wrong assumptions about, for instance,
> video timings.
>
> Logic is added to correctly get the sync signal based on the available displays
> in the DIGIT channel. The source is set only if both VENC and HDMI are supported.
>
> Signed-off-by: Ricardo Neri <ricardo.neri@ti.com>
> ---
> v3: instead of BUG_ON calls, select only if both VENC and HDMI are available.
I think they do make sense. For example, if somebody calls this function
and tries to set the switch to VENC on an OMAP that doesn't have VENC,
something is wrong. Your new version just skips the register write in
that case, which is ok, but I think we should also yell that something
is wrong.
I'd have the BUG_ONs there, but change them to WARN_ON. I think we
should generally try to have less BUGs and more WARNs. Also, please keep
the comment about the bits being written (VENC_HDMI_SWITCH), it helps to
understand the code.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-01 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 23:56 [PATCH v3 RESEND] OMAPDSS: DISPC: Improvements to DIGIT sync signal selection Ricardo Neri
2012-08-01 6:28 ` Tomi Valkeinen [this message]
2012-08-01 12:53 ` Ricardo Neri
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=1343802521.2645.6.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=ricardo.neri@ti.com \
--cc=s-guiriec@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 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).