From: Afzal Mohammed <afzal@ti.com>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
nsekhar@ti.com, hvaibhav@ti.com, linux-omap@vger.kernel.org,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Subject: [PATCH v2 00/10] video: da8xx-fb: runtime timing configuration
Date: Mon, 7 Jan 2013 10:31:30 +0530 [thread overview]
Message-ID: <cover.1357303978.git.afzal@ti.com> (raw)
Hi,
This series makes da8xx-fb driver (device found on DaVinci and AM335x)
capable of handling runtime timing configuration by adding fb_set_par.
The last change adds actual fb_set_par support. Other preceeding
changes makes the way clear for it as well as does certain cleanup's
on the way.
This has been tested on da850 evm as is. This was also tested on
am335x-evm & am335x-evmsk with a series that adds DT support which
follows shortly.
This is based on v3.8-rc2
Regards
Afzal
v2: disable raster in fb_set_par properly
Afzal Mohammed (10):
video: da8xx-fb: fb_check_var enhancement
video: da8xx-fb: simplify lcd_reset
video: da8xx-fb: use modedb helper to update var
video: da8xx-fb: remove unneeded "var" initialization
video: da8xx-fb: store current display information
video: da8xx-fb: store clk rate even if !CPUFREQ
video: da8xx-fb: pix clk and clk div handling cleanup
video: da8xx-fb: store struct device *
video: da8xx-fb: report correct pixclock
video: da8xx-fb: fb_set_par support
drivers/video/da8xx-fb.c | 181 +++++++++++++++++++++++++++-------------------
1 file changed, 105 insertions(+), 76 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-01-07 5:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 5:01 Afzal Mohammed [this message]
2013-01-07 5:04 ` [PATCH v2 03/10] video: da8xx-fb: use modedb helper to update var Afzal Mohammed
2013-01-07 5:05 ` [PATCH v2 05/10] video: da8xx-fb: store current display information Afzal Mohammed
2013-01-07 5:05 ` [PATCH v2 07/10] video: da8xx-fb: pix clk and clk div handling cleanup Afzal Mohammed
2013-01-07 5:05 ` [PATCH v2 08/10] video: da8xx-fb: store struct device * Afzal Mohammed
[not found] ` <cover.1357303978.git.afzal-l0cyMroinI0@public.gmane.org>
2013-01-07 5:04 ` [PATCH v2 01/10] video: da8xx-fb: fb_check_var enhancement Afzal Mohammed
2013-01-07 5:04 ` [PATCH v2 02/10] video: da8xx-fb: simplify lcd_reset Afzal Mohammed
2013-01-07 5:05 ` [PATCH v2 04/10] video: da8xx-fb: remove unneeded "var" initialization Afzal Mohammed
2013-01-07 5:05 ` [PATCH v2 06/10] video: da8xx-fb: store clk rate even if !CPUFREQ Afzal Mohammed
2013-01-07 5:06 ` [PATCH v2 09/10] video: da8xx-fb: report correct pixclock Afzal Mohammed
2013-01-07 5:06 ` [PATCH v2 10/10] video: da8xx-fb: fb_set_par support Afzal Mohammed
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=cover.1357303978.git.afzal@ti.com \
--to=afzal@ti.com \
--cc=FlorianSchandinat@gmx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=hvaibhav@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=rob.herring@calxeda.com \
--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).