From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit Taneja <archit@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/2] OMAPDSS: HDMI: Fix register dump of CORE registers
Date: Tue, 08 May 2012 15:04:44 +0300 [thread overview]
Message-ID: <1336478684.5761.30.camel@deskari> (raw)
In-Reply-To: <1336396828-29311-1-git-send-email-archit@ti.com>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Mon, 2012-05-07 at 18:50 +0530, Archit Taneja wrote:
> The HDMI CORE registers are dumped incorrectly due to incorrect register offset
> calculations. They are also dumped in a random order, with some of the registers
> repeated. This series fixes these issues.
>
> The patches apply over:
>
> git://gitorious.org/linux-omap-dss2/linux.git dev
>
> Tested on OMAP4 SDP.
>
> Archit Taneja (2):
> OMAPDSS: HDMI: Fix ti_hdmi_4xxx_core_dump
> OMAPDSS: HDMI: define and dump CORE registers in correct order
>
> drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c | 163 +++++++++++++++--------------
> drivers/video/omap2/dss/ti_hdmi_4xxx_ip.h | 57 +++++------
> 2 files changed, 109 insertions(+), 111 deletions(-)
Thanks, applying these.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-08 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 13:20 [PATCH 0/2] OMAPDSS: HDMI: Fix register dump of CORE registers Archit Taneja
2012-05-07 13:20 ` [PATCH 1/2] OMAPDSS: HDMI: Fix ti_hdmi_4xxx_core_dump Archit Taneja
2012-05-07 13:20 ` [PATCH 2/2] OMAPDSS: HDMI: define and dump CORE registers in correct order Archit Taneja
2012-05-08 12:04 ` Tomi Valkeinen [this message]
2012-05-08 12:09 ` [PATCH 0/2] OMAPDSS: HDMI: Fix register dump of CORE registers Archit Taneja
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=1336478684.5761.30.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
/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