public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: mythripk@ti.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 5/5] OMAPDSS: HDMI: Add support to dump clocks through
Date: Tue, 20 Sep 2011 16:31:17 +0300	[thread overview]
Message-ID: <1316525477.1949.20.camel@deskari> (raw)
In-Reply-To: <1316522954-16594-6-git-send-email-mythripk@ti.com>

On Tue, 2011-09-20 at 18:19 +0530, mythripk@ti.com wrote:
> From: Mythri P K <mythripk@ti.com>
> 
> Add support to dump the HDMI regm, regn, and other clock parameters.

This patch doesn't work at all. It's checking for CONFIG_OMAP2_DSS_HDMI,
whereas the actual define is CONFIG_OMAP4_DSS_HDMI. And even after
fixing that, the output is:

HDMI Clock Info
regm            104regmf 104
dcofreq 0regsd 1
DSS_FCK (DSS_FCLK)      (off)
hdmi fclk source = 3

Did you test your patches at all?

 Tomi



  reply	other threads:[~2011-09-20 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20 12:49 [PATCH 0/5] OMAPDSS: HDMI: Debug support and Register cleanup mythripk
2011-09-20 12:49 ` [PATCH 1/5] OMAPDSS: HDMI: Move the comments in avi infoframe mythripk
2011-09-20 12:49   ` [PATCH 2/5] OMAPDSS: HDMI: Replace hdmi_reg struct with u16 mythripk
2011-09-20 12:49     ` [PATCH 3/5] OMAPDSS: HDMI: Add missing register definitions mythripk
2011-09-20 12:49       ` [PATCH 4/5] OMAPDSS: HDMI: Add support to dump registers through mythripk
2011-09-20 12:49         ` [PATCH 5/5] OMAPDSS: HDMI: Add support to dump clocks through mythripk
2011-09-20 13:31           ` Tomi Valkeinen [this message]
2011-09-20 15:36             ` K, Mythri P
2011-09-20 15:42               ` Tomi Valkeinen
2011-09-20 13:29         ` [PATCH 4/5] OMAPDSS: HDMI: Add support to dump registers through Tomi Valkeinen

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=1316525477.1949.20.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mythripk@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