linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH 0/6 v3] fbdev: sh-mobile: HDMI support for SH-Mobile SoCs
Date: Wed, 21 Jul 2010 10:13:02 +0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1007211145420.16933@axis700.grange> (raw)

This patch set adds a static HDMI support to SH-Mobile SoCs, specifically, 
to sh7372 (ap4evb) in this version. "Static" means only 720p is supported 
ATM. Also hotplug support is implemented without changing the framebuffer 
geometry. Dynamic geometry reconfiguration is planned for a future patch.

This series now depends on an arm-shmobile runtime PM RFC patch from 
Magnus with my incremental patch to it [1].

Thanks
Guennadi

[1] http://thread.gmane.org/gmane.linux.ports.sh.devel/8457

---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

             reply	other threads:[~2010-07-21 10:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 10:13 Guennadi Liakhovetski [this message]
2010-07-27  7:20 ` [PATCH 0/6 v3] fbdev: sh-mobile: HDMI support for SH-Mobile SoCs Kuninori Morimoto

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=Pine.LNX.4.64.1007211145420.16933@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).