From: <mythripk@ti.com>
To: tomi.valkeinen@ti.com, linux-omap@vger.kernel.org
Cc: Mythri P K <mythripk@ti.com>
Subject: [PATCH v4 0/4] OMAPDSS: HDMI: Improve the timings logic in HDMI
Date: Fri, 6 Jan 2012 17:52:06 +0530 [thread overview]
Message-ID: <1325852530-4829-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.
changes since v3: Remove double call of function
changes since v2: Incorporate changes in find_timing function
changes since V1: change of hdmi_find_timing function to return pointer to the
timing struct rather than deep copy to timing structure passed as parameter
variable name change from temp to timing2 in comparator function.
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 | 256 +++++++++++++----------------
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, 135 insertions(+), 189 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-01-06 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 12:22 mythripk [this message]
2012-01-06 12:22 ` [PATCH v4 1/4] OMAPDSS: HDMI: remove duplicate video interface code mythripk
2012-01-06 12:22 ` [PATCH v4 2/4] OMAPDSS: HDMI: update static timing table mythripk
2012-01-06 12:22 ` [PATCH v4 3/4] OMAPDSS: HDMI: change the timing match logic mythripk
2012-01-06 12:22 ` [PATCH v4 4/4] OMAPDSS: HDMI: remove duplicate code and mode parameter mythripk
2012-01-09 7:01 ` [PATCH v4 0/4] OMAPDSS: HDMI: Improve the timings logic in HDMI 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=1325852530-4829-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).