dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Archit Taneja <architt@codeaurora.org>
To: robdclark@gmail.com
Cc: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
	Archit Taneja <architt@codeaurora.org>
Subject: [PATCH 0/3] drm/msm/hdmi: Some HDMI fixes for 8x96
Date: Fri, 16 Jun 2017 10:39:33 +0530	[thread overview]
Message-ID: <20170616050936.1280-1-architt@codeaurora.org> (raw)

Some fixes that makes HDMI more stable on 8x96:

- Make PLL switch to different freqs successfully (when switching between
  modes).
- Add AVI infoframes to reemove the pink strips seen on some monitors.
- Update some of the HDMI timing bitfields so that they can take in
  values > 4K.

The display bindings for 8x96 aren't in yet, so it's okay to have these
for 4.13.

Archit Taneja (3):
  drm/msm/hdmi: 8996 PLL: Populate unprepare
  drm/msm/hdmi: Updated generated headers
  drm/msm/hdmi: Fix HDMI pink strip issue seen on 8x96

 drivers/gpu/drm/msm/hdmi/hdmi.xml.h      | 59 +++++++++++++++++----------
 drivers/gpu/drm/msm/hdmi/hdmi_bridge.c   | 70 ++++++++++++++++++++++++++++++--
 drivers/gpu/drm/msm/hdmi/hdmi_phy_8996.c |  5 +++
 3 files changed, 110 insertions(+), 24 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation

             reply	other threads:[~2017-06-16  5:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  5:09 Archit Taneja [this message]
2017-06-16  5:09 ` [PATCH 1/3] drm/msm/hdmi: 8996 PLL: Populate unprepare Archit Taneja
2017-06-16  5:09 ` [PATCH 2/3] drm/msm/hdmi: Updated generated headers Archit Taneja
2017-06-16  5:09 ` [PATCH 3/3] drm/msm/hdmi: Fix HDMI pink strip issue seen on 8x96 Archit Taneja

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=20170616050936.1280-1-architt@codeaurora.org \
    --to=architt@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robdclark@gmail.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 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).