From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: stable@kernel.org, stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: OMAP4 HDMI PHY bug work-around for stable
Date: Tue, 28 Feb 2012 10:03:13 +0200 [thread overview]
Message-ID: <1330416193.2123.4.camel@deskari> (raw)
In-Reply-To: <1328787865.1909.64.camel@deskari>
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
Hi,
I haven't seen these merged nor any comment for these. Perhaps
stable@kernel.org was wrong address, so adding stable@vger.kernel.org
too.
I have added one additional fix into for-3.2-stable branch, which fixes
a problem with panel detection that the GPIO changes brought.
Tomi
On Thu, 2012-02-09 at 13:44 +0200, Tomi Valkeinen wrote:
> Hi,
>
> There is a hardware bug on OMAP4, which may cause the HDMI output to
> break irreversibly. A work-around for the bug has been merged into
> mainline, but is missing from stable.
>
> I've backported the necessary patches on top of 3.0, 3.1 and 3.2 stable
> trees, and pushed the following branches to:
>
> git://gitorious.org/linux-omap-dss2/linux.git
>
> fixes/for-3.0-stable
> fixes/for-3.1-stable
> fixes/for-3.2-stable
>
> 3.0 and 3.1 branches additionally contain a patch "OMAP: DSS2: HDMI: use
> default dividers", which fixes a problem with the HDMI clock divider.
> Without that the HDMI output won't start at all on those versions.
>
> The branches contain the following backported patches:
>
> OMAP: DSS2: HDMI: use default dividers
> OMAP: 4430SDP/Panda: use gpio_free_array to free HDMI gpios
> OMAP: 4430SDP/Panda: rename HPD GPIO to CT_CP_HPD
> OMAPDSS: remove wrong HDMI HPD muxing
> OMAP: 4430SDP/Panda: setup HDMI GPIO muxes
> OMAP: 4430SDP/Panda: add HDMI HPD gpio
> OMAPDSS: HDMI: PHY burnout fix
>
> Of those, the actual fix is in the last one, but as the GPIOs for HDMI
> were a mess, they needed some cleanup patches before the fix could be
> made.
>
> I'm not familiar with the process with stable kernels, so are the
> branches above fine to get them merged? Or should I send the patches
> with git-send-email?
>
> 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 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 11:44 OMAP4 HDMI PHY bug work-around for stable Tomi Valkeinen
2012-02-28 8:03 ` Tomi Valkeinen [this message]
2012-02-28 16:47 ` Greg KH
2012-02-29 9:07 ` Tomi Valkeinen
2012-02-29 14:57 ` Greg KH
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=1330416193.2123.4.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=stable@kernel.org \
--cc=stable@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).