From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: [GIT PULL] fbdev fixes#2 for 3.3
Date: Fri, 02 Mar 2012 20:36:41 +0000 [thread overview]
Message-ID: <4F512F59.9080901@gmx.de> (raw)
Hi Linus,
please pull these fixes for OMAP and viafb.
Thanks,
Florian Tobias Schandinat
The following changes since commit b01543dfe67bb1d191998e90d20534dc354de059:
Linux 3.3-rc4 (2012-02-18 15:53:33 -0800)
are available in the git repository at:
git://github.com/schandinat/linux-2.6.git fbdev-fixes-for-3.3-2
for you to fetch changes up to a3d0e4aecaa32001e02d5ce860d38f14095d06d2:
OMAPDSS: APPLY: make ovl_enable/disable synchronous (2012-02-29 22:42:28 +0000)
----------------------------------------------------------------
fbdev fixes for 3.3
It includes:
- two fixes for OMAP HDMI
- one fix to make new OMAP functions behave as they are supposed to
- one Kconfig dependency fix
- two fixes for viafb for modesetting on VX900 hardware
----------------------------------------------------------------
Archit Taneja (1):
OMAPDSS: HACK: Ensure DSS clock domain gets out of idle when HDMI is enabled
Florian Tobias Schandinat (3):
Merge branch 'for-3.3-rc' of git://gitorious.org/linux-omap-dss2/linux
into fbdev-for-linus
viafb: select HW scaling on VX900 for IGA2
viafb: fix IGA1 modesetting on VX900
Rob Clark (1):
OMAPDSS: HDMI: hot plug detect fix
Tomi Valkeinen (2):
OMAPDSS: panel-dvi: Add Kconfig dependency on I2C
OMAPDSS: APPLY: make ovl_enable/disable synchronous
drivers/video/omap2/displays/Kconfig | 2 +-
drivers/video/omap2/dss/apply.c | 6 ++++++
drivers/video/omap2/dss/hdmi.c | 24 +++++++++++++++++++++++-
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c | 9 +--------
drivers/video/via/hw.c | 4 ++++
5 files changed, 35 insertions(+), 10 deletions(-)
reply other threads:[~2012-03-02 20:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F512F59.9080901@gmx.de \
--to=florianschandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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