From: <mythripk@ti.com>
To: tomi.valkeinen@ti.com, linux-omap@vger.kernel.org
Cc: Mythri P K <mythripk@ti.com>
Subject: [PATCH 0/4] OMAPDSS: HDMI: Improve the timings logic in HDMI
Date: Fri, 11 Nov 2011 18:39:33 +0530 [thread overview]
Message-ID: <1321016977-1808-1-git-send-email-mythripk@ti.com> (raw)
From: Mythri P K <mythripk@ti.com>
There are some duplicate timing structure which are not needed thus removing
them to clean the code.
Also the static mapped timing structure is quite complicated to add new
timings, so simplify it by using array indexed method.
Mythri P K (4):
OMAPDSS: HDMI: remove duplicate video interface code
OMAPDSS: HDMI: update static timing table
OMAPDSS: HDMI: change the timing match logic
OMAPDSS: HDMI: remove duplicate code and mode parameter
drivers/video/omap2/dss/hdmi.c | 246 +++++++++++++----------------
drivers/video/omap2/dss/ti_hdmi.h | 14 +-
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c | 47 ++----
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.h | 7 -
4 files changed, 128 insertions(+), 186 deletions(-)
--
1.7.5.4
next reply other threads:[~2011-11-11 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 13:09 mythripk [this message]
2011-11-11 13:09 ` [PATCH 1/4] OMAPDSS: HDMI: remove duplicate video interface code mythripk
2011-11-11 13:09 ` [PATCH 2/4] OMAPDSS: HDMI: update static timing table mythripk
2011-11-11 13:09 ` [PATCH 3/4] OMAPDSS: HDMI: change the timing match logic mythripk
2011-11-11 13:09 ` [PATCH 4/4] OMAPDSS: HDMI: remove duplicate code and mode parameter mythripk
2011-11-14 7:33 ` [PATCH 3/4] OMAPDSS: HDMI: change the timing match logic Tomi Valkeinen
2011-11-16 5:31 ` K, Mythri P
2011-11-18 7:16 ` Tomi Valkeinen
2011-11-22 13:08 ` K, Mythri P
2011-11-14 7:20 ` [PATCH 2/4] OMAPDSS: HDMI: update static timing table Tomi Valkeinen
2011-11-16 5:13 ` K, Mythri P
-- strict thread matches above, loose matches on Subject: below --
2012-01-02 8:44 [PATCH 0/4] OMAPDSS: HDMI: Improve the timings logic in HDMI mythripk
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=1321016977-1808-1-git-send-email-mythripk@ti.com \
--to=mythripk@ti.com \
--cc=linux-omap@vger.kernel.org \
--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 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).