From: Thierry Reding <thierry.reding@gmail.com>
To: Dylan Reid <dgreid@chromium.org>
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org, swarren@wwwdotorg.org
Subject: Re: [PATCH 2/2] drm/tegra: Enable HDMI_5V_CON regulator
Date: Sat, 17 May 2014 23:34:57 +0200 [thread overview]
Message-ID: <20140517213456.GF1046@mithrandir> (raw)
In-Reply-To: <1400350881-22008-2-git-send-email-dgreid@chromium.org>
[-- Attachment #1.1: Type: text/plain, Size: 509 bytes --]
On Sat, May 17, 2014 at 11:21:21AM -0700, Dylan Reid wrote:
> The DDC bus uses this for it's supply, enable it so EDID can be read.
> This eliminates I2C read timeouts on Venice2 and EDID can be verified
> with i2cdump.
>
> Signed-off-by: Dylan Reid <dgreid@chromium.org>
> ---
> drivers/gpu/drm/tegra/hdmi.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
Like I said in reply to 1/2, this should be fixed by:
0d6696438d2c drm/tegra: hdmi - Add connector supply support
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-05-17 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 18:21 [PATCH 1/2] ARM: tegra: Mark Tegra124 HDMI compatible with Tegra114 Dylan Reid
[not found] ` <1400350881-22008-1-git-send-email-dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-05-17 18:21 ` [PATCH 2/2] drm/tegra: Enable HDMI_5V_CON regulator Dylan Reid
2014-05-17 21:34 ` Thierry Reding [this message]
2014-05-17 21:33 ` [PATCH 1/2] ARM: tegra: Mark Tegra124 HDMI compatible with Tegra114 Thierry Reding
2014-05-18 2:28 ` Dylan Reid
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=20140517213456.GF1046@mithrandir \
--to=thierry.reding@gmail.com \
--cc=dgreid@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.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