From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
mythripk@ti.com, archit@ti.com, x0132446@ti.com
Subject: Re: [PATCH 0/6] OMAPDSS: HDMI PHY burnout fix
Date: Fri, 20 Jan 2012 14:49:18 +0000 [thread overview]
Message-ID: <20120120144918.GM22818@atomide.com> (raw)
In-Reply-To: <1326804542-22285-1-git-send-email-tomi.valkeinen@ti.com>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [120117 04:16]:
> The main patch in this set is the last one, which implements a fix for the HW
> bug on OMAP4 which causes physical damage to the board if the HDMI cable is not
> connected but HDMI output is enabled.
>
> The preceding patches are small cleanups/fixes for HDMI GPIOs so that the fix
> can be implemented.
>
> Note that I haven't gotten a confirmation that using LDO_ON for the HDMI PHY
> power fixes the issue. So whether the fix works or not is unclear.
Feel free to merge via fb tree. For the arch/arm/*omap*/* parts:
Acked-by: Tony Lindgren <tony@atomide.com>
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
mythripk@ti.com, archit@ti.com, x0132446@ti.com
Subject: Re: [PATCH 0/6] OMAPDSS: HDMI PHY burnout fix
Date: Fri, 20 Jan 2012 06:49:18 -0800 [thread overview]
Message-ID: <20120120144918.GM22818@atomide.com> (raw)
In-Reply-To: <1326804542-22285-1-git-send-email-tomi.valkeinen@ti.com>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [120117 04:16]:
> The main patch in this set is the last one, which implements a fix for the HW
> bug on OMAP4 which causes physical damage to the board if the HDMI cable is not
> connected but HDMI output is enabled.
>
> The preceding patches are small cleanups/fixes for HDMI GPIOs so that the fix
> can be implemented.
>
> Note that I haven't gotten a confirmation that using LDO_ON for the HDMI PHY
> power fixes the issue. So whether the fix works or not is unclear.
Feel free to merge via fb tree. For the arch/arm/*omap*/* parts:
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2012-01-20 14:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 12:48 [PATCH 0/6] OMAPDSS: HDMI PHY burnout fix Tomi Valkeinen
2012-01-17 12:48 ` Tomi Valkeinen
2012-01-17 12:48 ` [PATCH 1/6] OMAP: 4430SDP/Panda: use gpio_free_array to free HDMI gpios Tomi Valkeinen
2012-01-17 12:48 ` Tomi Valkeinen
2012-01-17 12:48 ` [PATCH 3/6] OMAPDSS: remove wrong HDMI HPD muxing Tomi Valkeinen
2012-01-17 12:48 ` Tomi Valkeinen
2012-01-17 12:49 ` [PATCH 4/6] OMAP: 4430SDP/Panda: setup HDMI GPIO muxes Tomi Valkeinen
2012-01-17 12:49 ` Tomi Valkeinen
2012-01-17 12:49 ` [PATCH 5/6] OMAP: 4430SDP/Panda: add HDMI HPD gpio Tomi Valkeinen
2012-01-17 12:49 ` Tomi Valkeinen
2012-01-17 20:32 ` Archit
2012-01-17 20:44 ` Archit
2012-01-18 6:39 ` Tomi Valkeinen
2012-01-18 6:39 ` Tomi Valkeinen
2012-01-17 13:04 ` [PATCH 6/6] OMAPDSS: HDMI: PHY burnout fix Tomi Valkeinen
2012-01-17 13:04 ` Tomi Valkeinen
2012-01-20 14:49 ` Tony Lindgren [this message]
2012-01-20 14:49 ` [PATCH 0/6] OMAPDSS: HDMI " Tony Lindgren
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=20120120144918.GM22818@atomide.com \
--to=tony@atomide.com \
--cc=archit@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mythripk@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=x0132446@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.