From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: "linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
linux-omap mailing list <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] OMAP DSS fixes for 3.3-rc
Date: Tue, 28 Feb 2012 18:08:07 +0200 [thread overview]
Message-ID: <1330445287.2123.236.camel@deskari> (raw)
In-Reply-To: <4F4CFAD1.1000301@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
On Tue, 2012-02-28 at 16:03 +0000, Florian Tobias Schandinat wrote:
> On 02/23/2012 09:22 AM, Tomi Valkeinen wrote:
> > Hi Florian,
> >
> > Two fixes for OMAP DSS for 3.3:
> >
> > First one gets the HDMI output working again. Managing the clocks for
> > OMAP4 is not very simple, and this patch circumvents the problems we
> > have in the clock framework. It's a clean but rather hacky fix, but it
> > shouldn't cause any side-effects. The issue will hopefully be fixed
> > properly with DT when we'll get proper parent-child hierarchy for DSS HW
> > submodules.
> >
> > The second one is a simple fix for HDMI hotplug detection, which I
> > missed when I wrote the HDMI PHY fix
> > (c49d005b6cc8491fad5b24f82805be2d6bcbd3dd).
>
> Merged. You would add
> Cc: stable@vger.kernel.org
> to patches if appropriate?
Thanks. Yes, I have sent a separate mail to stable list, as the patches
needed some tuning to apply.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-28 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 9:22 [GIT PULL] OMAP DSS fixes for 3.3-rc Tomi Valkeinen
2012-02-28 16:03 ` Florian Tobias Schandinat
2012-02-28 16:08 ` Tomi Valkeinen [this message]
2012-02-29 1:42 ` Jingoo Han
2012-02-29 1:18 ` Jingoo Han
-- strict thread matches above, loose matches on Subject: below --
2012-01-26 12:07 Tomi Valkeinen
2012-01-30 5:22 ` Florian Tobias Schandinat
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=1330445287.2123.236.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=FlorianSchandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@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